[This message was posted by David Rosenborg of Pantor Engineering AB <[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/536b0dd0 - PLEASE DO NOT REPLY BY MAIL.]
Oops, typo, should have read "subtraction length" where I wrote "length preamble". /David > Only the subtraction length is nullable in a nullable string delta. So > the empty string that follows the length preamble in this case should be > encoded as single 0x80. You can find more information about empty > strings in the table in section 10.6.3 of the specification. > > /David > > > Since the optional delta operator is nullable, if the substraction > > length is not null, is the string that follows also handled as a > > nullable string? It makes sense that at times an empty string is what > > would be desired, allowing the base value string to be cut off at the > > front or back. I could not find where the specification addressed this > > question. I'm wondering about these two cases: > > > > A. stream input:(0)0000000 (1)0000000 (not nullable assumption) is the > > "\0" string B. stream input:(0)0000000 (1)0000000 (nullable > > assumption) is the empty string. [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 -~----------~----~----~----~------~----~------~--~---
