Yes I agree that is odd. This could stumble you if you were conditionally putting empty into items, and then acting on an empty value. The last item would never get processed because it would no longer exist! It goes against the principle that for computers, empty is not the same as nothing. NULL is nothing. Empty is in terms of a Livecode string a value that still is taking up an address in memory.
I guess it’s one of those oddities of Livecode we learn to live with. I suppose if were an issue, I would use an array instead. But it is inconsistent, and so is deleting the last line if you put empty into it. After all, we have DELETE if we really wanted to REMOVE the last word or item or line. put empty into should not work differently just because it is the last token we are working with. Bob On Mar 19, 2014, at 23:08 , Kay C Lan <lan.kc.macm...@gmail.com<mailto:lan.kc.macm...@gmail.com>> wrote: put 1,2,3,4 into tStore put the number of items in tStore into msg --gives 4 put empty into item 2 of tStore put empty into item 4 of tStore put the number of items in tStore into msg --gives 3 _______________________________________________ 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
