global problems
Jon
jbondy at sover.net
Tue Aug 2 08:01:33 EDT 2005
"In other languages, if you removed all references to a global and
recompiled, of course it would disappear...? "
Exactly! This is SO counterintuitive, no matter how useful it might be
I NEVER would have even considered that the language might behave in
this way. Another issue for the Intro For Newbies?
:)
Jon
Brian Yennie wrote:
> Global properties do!
>
> For me, the rationale is simple: globals are the ONLY way to have data
> which is _not_ stack specific. As such, closing or modifying a stack
> should never delete global data.
>
> Perhaps what you're really looking for is a stack-level local variable?
>
> I'm thinking the seeming oddity of the situation has something to do
> with the loose restrictions on declarations in xTalk, and the runtime
> nature. In other languages, if you removed all references to a global
> and recompiled, of course it would disappear...?
>
>> Right... well, the point I was trying to make is that there's
>> *nothing* else that has this persistence. Maybe I chose a bad example.
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
More information about the use-livecode
mailing list