francis@mirror.UUCP (Joe Francis) (12/16/89)
In article <9291@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes: > The syntax would be >"list^^.refCon = LONGINT(<whatever>);" if I remember my Pascal. I've forgotten my Pascal, too, so there may be more wrong than just the missing colon before the equal sign. >You can also track the general flow of execution in various other >ways. If you're not sure a piece of code is getting executed, put a >SysBeep in it. What's with SysBeep, anyway? I taught myself what I know about C and the Mac both (counting reading IM, tech notes, and these wonderful notes as "teaching myself", that is), and I got real embarassed when I interviewed for a mac programming position (which I was nowhere near qualified for - some headhunters will send you to any interview). What happened was: My application called SysBeep. The interviewer was testing my app on a mac equipped with a humongous SysBeep sound (I don't know if it was using MasterJuggler or what). My app crashed. At the time my app had a very naive memory management, and strenthening this cured the problem. I was surprised that SysBeep wanted application memory, though. Is this true? Does SysBeep place the sound resource in the application heap? What's going on here? Thanks for any insight, and if your feeling generous with your knowledge, I would appreciate any info on routines which can potentially request large amounts of app memory, or eat large amounts of stack space, especially if they do not indicate this in IM documentation. -------------------------------------------------------------------------- SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM Joe Francis | Nobody expects francis@prism.TMC.COM or | the Spammish francis@mirror.TMC.COM | Repitition! --------------------------------------------------------------------------