Right, it looks like something in the message box message box interpretation scripts changed between the various releases I tested.
I guess I should file a bug report. Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> On Fri, Nov 14, 2014 at 10:38 AM, J. Landman Gay <jac...@hyperactivesw.com> wrote: > On 11/14/2014, 11:58 AM, Peter Haworth wrote: > >> My feeling is that something changed in the message box parsing routines >> and the semicolon is being taken as a separator between two statements. >> > > A semicolon in any script is interpreted as a line ending, except when > within quotation marks. If the example failed (where the semicolon is > within the quotes) then that would be a problem with the scripts that > interpret the message box content. > > That said, it is very tricky to implement code correctly in all cases from > the message box because of the "do" statements and other contortions it > needs to use. Ideally, tests should always be conducted from the script > editor where the intermediate interpretive layer isn't present. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > > _______________________________________________ > 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
