Hi Craig, I don't know if it is compelling, but a constant is readily available to all handlers in a script. If you have a library with functions and you don't know which function will be called first, it is useful to not be required to define a local variable in every function. Usually, I keep constants at the top of a script, which makes it easy to adjust a script for different customers or servers. Sometimes, I use a constant only because it is easier to write, e.g. I consistently use dot instead of ".".
-- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 Download the Installer Maker plugin for Runtime Revolution at http://qurl.tk/ce Create installers for Mac and Windows on *every* Rev-compatible platform. No additional software needed. On 14 okt 2010, at 18:28, [email protected] wrote: > About the constant command that Phil used in his process gadget. What does > it do that a variable does not? I see it cannot be altered in the same > handler, and I see that it can overRide a built-in constant, which might be > useful. Anyone ever come up with a compelling reason to use such a thing? > > Craig Newman _______________________________________________ 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
