David Megginson wrote: > I'm not sure if that's a good idea -- I'd be more inclined to default > to 0/false/empty-string. What do other people think?
Actually, thinking about this more, I'm starting to like this idea. As you say, it's really the same thing as changing the default value for a boolean property. For numbers, we clearly want to default to 0, of course. And for strings an empty string. But for booleans, defaulting to true makes sense -- it is the "presence" of the tag that is true. If it wasn't there, then false makes perfect sense too. This would require changing the defaulting semantics, though. The "default" value you fill in at parse-time should be true, but the "default" you fill in when a non-existent property is queried should be false. I'm not sure how hard that would be. Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
