Melchior FRANZ wrote: > * Tim Moore -- Tuesday 07 April 2009: >> How / where do you document that a parent node requires this explicit >> listener activation? > > How/where do we document that the heading is in degree, not radian? > > How/where do we document that a value is normalized (0-1), not an > angle? > Beats me, but I'm not the one claiming that the property list format is self-documenting. > Adding a suffix would be a possibility. After all, just like > in the case of "-ft" or "-m" suffixes, it's only meant for the > human user or coder, so that s/he knows how to handle the type. > The code itself knows it, because it's written that way. The listener > of the <color-at> (or <color-atomar>) node knows it without looking > at the node name. That's just business as usual, not a new challenge. Right, so it's (mostly) the Nasal programmer who would have to know the suffix.
Tim ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
