[EMAIL PROTECTED] wrote:
> > Thanks for the info. Does the above check guarantee that the local variable is
> > actually allocated on the stack? With respect, what
> > if the compiler was using a register to store the local variable?
>
> Well, if the compiler didn't put the variable on the stack, then how could it
> generate its address? It can't, therefore, the variable *is* on the stack.
> QED.
Actually, I figured this out after I posted. Apologies.
> > Why not use the value of the A7 register instead?
>
> Because that would require hacking up a little assembly code to fetch it.
> Taking the address of a local variable is good enough and doesn't require
> assembly.
Fair comment.
> Well, allocating your own stack would explain a lot. If the stack pointer is in
> this seperate block, then it's outside the range returned by SysStackInfo.
SysGetStackInfo returns the start and end of stacks as setup by app prefs. As you can
see from my code, I setup the app prefs.
Thus, from what I can see, my code should work.
> If you want a larger stack, then use the mechanism for creating a larger
> application by specifying the value you want in the application's 'pref'
> resource.
I was under the impression that the pref#0 resource is not available for PalmOS 2. I
am still trying to support PalmOS 2 (and now
wondering if I should be bothering).
Thanks again for the info.
Kind regards,
--
Christopher Hunt
Class Action Pty. Ltd.
Complete time zone management for the Palm(tm) connected organizer.
Check out http://www.classactionpl.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
