connamara/quickfixn — Issue #52: Message fields are not nullable and have no proper way to say they have no value
Author: NetTecture
Created: 2012-03-09 21:36:35+00:00
State: open

This can get nasty for optional fields - requires a ton of try/catch which is not only ugly as hell but also slow (always creating a stack frame context).

The proper .NET way would be if fields that are not natively nullable (classes as strings) are Nullable which has full .NETsupport and a nice .HasValue field.