Unwanted Explicit variables set to true?
jerry at daniels-mara.com
Thu Oct 12 11:35:25 EDT 2006
In Galaxy (and I believe in Constellation) the explicit vars property
is only set during a compile, and then it is set according to the
explicit var setting that is "attached" to the object being compiled.
This is a Galaxy/Constellation convention.
SO...I don't think it's entirely accurate to say Constellation or
Galaxy has its own setting, but rather the object itself. Small
difference, but an important one.
Tool makers for the 21st century
On Oct 12, 2006, at 10:23 AM, Stephen Barncard wrote:
> I had this problem and found out it was Constellation, it has it's
> own settings for explicitvariables. But you didn't mention it, I know.
>> Hmmm. Recently, 2.7.2 on OS X started to behave as if
>> explicitvariables was set to true. Perfectly functioning scripts
>> opened in the editor would generate unquoted literal errors and
>> moaning about undeclared variables.
>> I today moved to 2.7.4, confident that the problem would go away,
>> but it hasn't - 'put the explicitvariables' in the message box
>> returns false. Setting it to false changes nothing.
>> I found nothing on this in the archives since 2003. Que pasa?
>> Best Wishes,
>> David Glasgow
>> Carlton Glasgow Partnership
> stephen barncard
> s a n f r a n c i s c o
> - - - - - - - - - - - -
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode