Socket reading problem
len-morgan at crcom.net
Sun Feb 19 21:11:14 CST 2012
On 2/19/2012 8:50 PM, Mark Wieder wrote:
> Sunday, February 19, 2012, 5:25:32 PM, you wrote:
>>> LC doesn't know from uints. Your best bet is to read them as chars (or
>>> more precisely as bytes), as you're doing in your second example.
>> I thought this was true until I looked it up in the dictionary. It
>> states that those are valid chunkTypes. Has that changed from 4.5 to
>> 5.0? To be honest, I don't remember seeing that there before today and
>> it would have been handy. Also available: int, int2, int4, uInt, uInt2,
>> uInt4 - at least according to the dictionary.
> Well whaddya know about that! I'm gonna have to rtfm one of these
> days. Grasping at straws here, you specified "uInt2s" rather than
> "uint2" ... it's possible that the plural form doesn't work.
If you look at the last example in the dictionary, it says "... 30
uInt2s" so I'm guessing that the plural form is ok. However, doesn't
seem to work either way. This would be very handy if I could make it work.
More information about the use-livecode