[This message was posted by Dale Wilson of Object Computing, Inc <[email protected]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/f89eac9d - PLEASE DO NOT REPLY BY MAIL.]
> In FAST (Version 1.1) Encoding, [0x00 0x00] = "\0" and [0x00] = Empty > String. But when we decoding those values into Application Variables We > have to face some difficulties because There is no difference between > Null Terminated String and Empty string in programming level. Some programming languages allow strings of 8 bit characters to contain any bit pattern, including a byte of all zeros. Others do not, or at least they make it difficult. One of the beauties of FAST is is doesn't impose its own restrictions on the data. You should never run into a case where you say "I want to send this information, but FAST won't let me do it." That being said, it is rare to actually need strings containing null bytes, so if you are coding to a single application, you don't have to worry about the support for null bytes in strings. It's only if you are producing a general purpose FAST implementation, or if your specific application uses embedded nulls that you would have to handle this case. Dale Dale [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
