Joseph Kesselman wrote: > And frankly, I'm not convinced that Boolean.TRUE/FALSE/null is really more > legible than yourownclass.YES/.NO/.UNKNOWN. The resulting code doesn't > look a heck of a lot different.
In terms of legibility, it's probably the same. But we have to think about what this represents here -- a feature state. And features are booleans. That's the way they were defined in SAX2 and it's been that way ever since. I think switching to something other than a boolean/Boolean would confuse users. > In internal methods/values, Boolean-and-null for a tristate value wouldn't > bother me. In an API, it feels like an accident waiting to happen. This is the Xerces *Native* Interface, by the way. And I disagree with your assessment that this is an accident waiting to happen. :) -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
