> > It seems > >more logical to always assume variables will be evaluated prior to script > >execution. > > Yes, but the man page doesn't say that it's a variable: it says that > the <i>property</i> thing in the "set" statement is the name of a > property. The name. Not "a variable evaluating to a name". And I > think that needs to be pointed out explicitly, because the obvious > possibilities are 1/ only the actual name is allowed 2/ any > expression giving a name. I don't understand at all why here only a > name or a variable is allowed.
You are right. I don't see why if the engine can evaluate a variable it can't also evaluate an expression. All I know is that you get a compile time error if you put an expression there. Perhaps it should be feature requested??? Monte _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
