On Saturday, 09/21/2002 at 04:30 ZE9, Andy Clark <[EMAIL PROTECTED]> wrote: > And features are booleans.
But, as you note, this value is not a boolean value. It's tristate. By switching to Boolean you're already taking a step away from that simple view. If you really want to stick with booleans it could be done by "piggybacking" two features, so you've got two bits to work with. > > 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. I'm aware of that. XNI is still an API you're expecting folks to code against; witness NEKO and revalidaton. > And I disagree with your assessment that this is an > accident waiting to happen. :) We agree that we disagree, then. <grin/> That's fine; thesis plus antithesis yield synthesis. ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
