You're not going totally crazy, unless I am too. This fails here in LC7.0.1 on Mac OS X 10.10.1…
on mouseUp put 1.884956 into tVar put value(tVar + 0) end mouseUp …With the following error; button "A": execution error at line 3 (value: error executing expression) near "1.884956", char 1 But this works… on mouseUp put 1.884955 into tVar add 0.000001 to tVar put value(tVar + 0) end mouseUp …And this works; on mouseUp local tVar = "1.884956" put value(tVar + 0) end mouseUp Then if you use Try/Catch, they all fail in LC7.0.1, but work in LC5.5.5! Paul. :-/ > On Jan 14, 2015, at 3:06 PM, Graham Samuel <livf...@mac.com> wrote: > > Thanks to those who replied. So, I am going crazy! I suppose it is something > very particular about my setup. I did find one other way to show the anomaly, > which was to put > > put 1.884956 into it; put value(it+0) > > this gives me the error > "Message execution error: > Error description: value: error executing expression > Hint: 1.884956" > But of course YMMV. I am quite happy to be told it’s my fault, but the fact > is that this is just an abstraction of something that has arisen in the > middle of a loop that produces a table of values based on input parameters > which are all very similar: the loop suddenly hits an error only on this > particular value. It has worked in earlier versions of LC, but now I’m wedded > to Unicode, it’s got to work with LC 7. > > If I ever get an explanation, I’ll tell the list about it. > > Cheers > > Graham >> On 14 Jan 2015, at 23:48, Roger Guay <i...@mac.com> wrote: >> >> Graham, >> >> I get true in both cases, same setup. >> >> Roger >> >>> On Jan 14, 2015, at 1:03 PM, Graham Samuel <livf...@mac.com> wrote: >>> >>> Using LC 7.0.1 on Yosemite 1010.1, when I type this into the message box >>> >>> put (1.884955 is a number) >>> >>> I get true, as expected, but if I put >>> >>> put (1.884956 is a number) >>> >>> I get >>> >>> Script compile error: >>> Error description: Expression: unquoted literal >>> >>> This result was derived from some complex code so I originally thought that >>> the character string could have been corrupt with invisible characters, >>> but I retyped the numbers myself. This seems so mad that I need someone to >>> confirm it, even though I find it completely repeatable. I tried it on LC >>> 6.7 (which just happens to be on my machine) and I got true as expected. >>> >>> Someone tell me I am not crazy. >>> >>> TIA >>> >>> Graham >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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
