Do you mean that if you declare and load a global, say "yourGlobal", that you should be able, in any other script, to just write:
answer yourGlobal and retrieve that data? I find that variables, script local variable and globals are treated just right. I could be old-fashioned, though. Craig Newman -----Original Message----- From: Mark Stuart <mfstu...@cox.net> To: use-livecode@lists.runrev.com Sent: Wed, Jul 6, 2011 10:56 pm Subject: defining and using globals in an application Hi all, To me, once globals are defined and put with a value, their value should be available from any stack within the application. So far, so good. But the problem arises where, within other stacks script, if you don't define the required global again, the desired value is not there. The result is the name of the global in the stack where that global was first defined. Not good. So why aren't the values of global's, global to the application? In other software development languages, this IS the case. Wouldn't you want the same in LC? I would. Why isn't this the case in LC? Regards, Mark Stuart _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
