On 12/23/05 4:21 PM, "Alex Tweedly" <[EMAIL PROTECTED]> wrote: >@pByReference , 'r' for parameter by reference
I agree, this is X-talk, not Pascal or C where the register address is important for stack heap management (here it means memory stack) On my hard drive, I am to the point where I have to manage a heap of stacks according to my memory, but the computer is always managing the stack heap in its memory... and when it goofs... time to reboot the computer. Good explanation of the scope. Jim Ault Las Vegas On 12/23/05 4:21 PM, "Alex Tweedly" <[EMAIL PROTECTED]> wrote: > Or you can pass the parameter by reference; in that case, there is not a > separate, new variable - and any changes made within the handler are > made to the actual variable. You do this by prepending an "@" to the > parameter name, as in > > >> on myhandler @pByReference >> ... >> add 1 to pByReference >> ... >> end myhandler > > > and the effect is to increment the variable passed to the handler. > > I have always thought that this would warrant a separate naming > convention (e.g. 'r' for parameter by reference, instead of 'p' for > parameter) - though in fact I haven't used it often enough to feel that > was important for me. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
