FWIW, the Rev Dictionary defines stacksInUse as a property, not a function, and "put stacksInUse()" from the Message Box returns an error.
Get some rest, Richard. :{`)
I need it, but this is a language subtlety that has conused me even when well rested.
I tend to think of a token for read-only data that can only be determined at runtime as a function. After all, if the stacksInUse is a property one might expect to be able do something like:
set the stacksInUse to empty
I just tried that and it says I can't modify that "property", yet indeed I have complete control over its value, only I have to use "stop using" in a loop rather than the "set" command, which is otherwise the cardinal way to set the value of a property.
So is it truly behaving more like a property than a function?
"The" is no help here, as it can be optionally used with many functions while being required for most properties (though I've never seen the benefit of also allowing it for functions; it seems to slow learnability, evidenced perhaps only by my confusion on this after 15 years <g>).
By what rules could one intuit whether a given token is a function or a property?
Jeanne, what's Kamins' argument for this one?
And what is the rule that determines when "the" is necessary? Is it required for custom props only, and optional with all others?
-- Richard Gaskin Fourth World Media Corporation ___________________________________________________________ [EMAIL PROTECTED] http://www.FourthWorld.com _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
