[This message was posted by Hanno Klein of Deutsche Börse Systems 
<[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/6cbac6c0 - PLEASE DO NOT REPLY BY MAIL.]

If I am not mistaken, zero is the NULL value and all "real" integers are 
shifted by one, i.e. 0 is 1, 1 is 2 etc. on the wire. The decoder then needs to 
subtract 1 to provide the real value to the application. Zeor on the wire then 
represents the NULL value and can be given to the application in whatever way 
it expects to see NULL values.

> I knwo this is probably a ver simple question BUT how is a UInt32 field 
> defined as having null support in the template defination?


[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.

  • [FIX] Re: Nullable Integers in ... 'FAST Protocol' forum at fixprotocol . org

Reply via email to