Serial I/O is unfortunately missing messages. Are you thinking of sockets?
I almost always use send. When implementing “blocking” when a customer asks for it (as in a sockets-like implementation on iOS), I might use wait with messages or even wait for message, but that requires flags when I don’t want recursion. With send, things can start and end in any order. DAr On May 16, 2014, at 5:50 PM, Jerry Jensen <j...@jhj.com> wrote: > On May 16, 2014, at 4:32 PM, Richard Gaskin <ambassa...@fourthworld.com> > wrote: > >> Dar Scott wrote: >> >>> I don’t see this in the ‘repeat’ entry in the dictionary. >> >> "with messages" is a modifier for the "wait" command - you'll find it >> documented there. > > I use the wait with messages all the time in a project that takes data from > serial ports that can send to me without warning. Its very useful. > > So how could I presume that it would work the same way tacked onto a repeat > statement? > > Would you like me to file a documentation bug report, or am I missing > something? > > .Jerry > > > _______________________________________________ > 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
