It seems that the general consensus is to immediately test for a null value and throw a TProtocolException indicating that Null values/keys are not allowed in collections .
On Tue, Sep 9, 2008 at 3:31 AM, Johan Stuyts <[EMAIL PROTECTED]> wrote: > For this reason, my vote is that this is the correct behavior and we >> should not support null values in containers. >> > > I agree, and I also think it should be enforced in all languages. It is > better to encounter limitations up front (even if your language does not > have that limitation) instead of after lots of code has been written. For > example, if a language that does not support null values in containers needs > to access the services in the future, you won't be required to review all > service implementations and modify the ones that put null values in > containers. > > -- > Kind regards, > > Johan Stuyts >
