A caveat, however; test "everything" before you rely on it. NO EXCEPTIONS! Particularly when you make major changes to the your "systems". Often that may be accomplished by merely running something that you have done previously that worked before. If you have several very different somethings to run, that should provide some sense of security. I'm sure this approach is "old hat" to most of you, but?...
Joe Lewis Wilkins Architect and Director of Product Development for GSI On Sep 20, 2011, at 9:16 AM, Andre Garzia wrote: > Tereza, > > No it is not crazy... > > can we assume that arrayencode always encode the same way? because this way > you can simply arrayencode both values and compare them... > > andre > > On Tue, Sep 20, 2011 at 12:45 PM, Tereza Snyder <ter...@califex.com> wrote: > >> >> Is it crazy to assume that if "=" works, then "<>" (or in other languages, >> "!=") would also? >> >> >> On Sep 20, 2011, at 10:27 AM, Robert Brenstein wrote: >> >>> On 19.09.2011 at 16:04 Uhr -0500 Tereza Snyder apparently wrote: >>>> Look at the docs for "="; LiveCode CAN compare arrays using "=". >>> >>> Ah, something new learned; yes, to quote the docs: >>> >>> The ability to compare two arrays using = was added in version 3.5. >> Previously, comparing two arrays would have converted both arrays into the >> empty string, and always returned true. >>> >>> The docs mention comparing arrays only for the = operator. >>> >>> Robert >>> _______________________________________________ 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
