> I would say that's the only thing that makes sense; initializing a MIME type > with NULL should be equal to it not being initialized. I don't think it's > worth > resembling BeOS behavior here. I have updated BMimeType in hrev43858 so that 2 uninitialized BMimeType objects are considered equal and an uninitialized BMimeType object is considered to be equal to one that is initialized to NULL. In terms of the program above the results are now: m1 == m2 m1 == NULL m3 == m4 m3 == NULL I have noted in the doxygen comments in the source that this is an intentional break from BeOS R5. That should eventually make its way into the Haiku Book so that this incompatibility will eventually be documented. Thank you, John Scipione