[EMAIL PROTECTED] wrote:
I noticed in the standalone builder, you can set the destroy stack to true.
What's the significance of that?
<joke>
The destroyStack property is an option for masochists: it gives you the
ability to conveniently destroy whatever you've been working on. Weeks
or even months of hard work can be destroyed with a simple click of a
checkbox.
</joke>
:)
I'm just kidding. It actually does nothing destructive to your stack
file at all, but is merely a poor choice of term for what it really does:
The destroyStack property purges the stack from memory when it's closed.
It can be handy on system with minimal RAM.
It's really not as scary as it implies. I feel it could benefit from
being depricated in favor of something that more closely describes that
it actually does: "purgeStack".
<noJoke>
There are only a handful of tokens in the language I feel are so bad
they should be depricated, but this is definitely at the top of my list.
It scares every newcomer who encounters it, creating a frightening
learning obstacle for something that is really quite simple and not
frightening at all, if only given an appropriate name. I'm sure
destroyStack makes perfect sense to a UNIX veteran working in C, but to
everyone else it's just a problem.
If you feel similarly see the Bugzilla report titled:
"destroyStack" is an unnecessarily scary term
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=1072>
</noJoke>
--
Richard Gaskin
Fourth World Media Corporation
__________________________________________________
Rev tools and more: http://www.fourthworld.com/rev
_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution
