Feb 96 Factory Floor
Volume Number: 12 Issue Number: 2$ #Column Tag: From The Factory Floor| From the Factory Floor =A monthly column of assorted news, interviews, and technical information from Metrowerks. By Dave Mark U Note: Source code files accompanying article are located on MacTech CD-ROM or„ source code disks. SIn last month’s issue, we introduced a brand new column with little in the way of Yexplanation. Here’s the skinny. At Neil’s persistent urging, the folks at Metrowerks Wasked me to put together a regular monthly column, but with no particular agenda. For Sexample, last month’s column was a Java interview with Greg Galanos, Metrowerks’ TPresident and CEO. This month, we’ll go through a pile of Metrowerks tech support Wquestions and answers. Got any ideas? Any interviews you’d like to see? As always, Myour feedback is most welcome. Check out page 2 of the magazine for contact information. QThe questions were provided by Stephen Chong, Khurram Quereshi, and the folks at [Metrowerks tech support. I did a little bit of editing just to clean up the questions but ZI tried to keep with the spirit of the original question. Since not everyone wants their ?name up in lights, I didn’t include names with the questions. Top Ten Tech Support Questions NQ: My program makes extensive use of SIOUX for console i/o, and I frequently $Rgenerate more than 32K worth of output in the console window. I’ve noticed that $Rwhen I scroll down to the bottom of my console window, I occasionally end up with$Lgarbage in the window and sometimes the window stops scrolling. Any ideas?/SA: Our SIOUX output window can only handle 32k of output at a time, and after you;$Nsend it more than that, results are unpredictable. The solution is to eitherG$Uredirect stdout to a file (via the ccommand() function/dialog in console.h) orS$8change the printfs to fprintfs and write to a file.zMQ: How can I use the debugger for debugging MPW tools and how can I specify $,command-line arguments when I am debugging? TA: Currently, our debugger doesn’t support debugging MPW tools. One option is to $Rbuild your tool as an application that uses the ccommand() function to take its$Lcommand-line arguments and I/O redirection. Once it is debugged, you would $Nchange the project type back to MPW tool, swap ANSI libraries, and remove the›$Rccommand call. Another option is to purchase Steve Jasik’s The Debugger, whichÈ$0can debug 68K MPW tools, and possibly PPC ones.UQ: In the following code snippet, the scope of the variable i inside the for-loop