Melchior FRANZ wrote: > * Buganini -- Friday 20 March 2009: >> IMO, if these compound types are unavoidable, [...] > > They are very much avoidable. We've had colors and coordinates since > *ages*. And what next? If we have VEC3, then what about POSITION, > which contains latitude/longitude/altitude, and ORIENTATION with > heading, pitch, roll, Those are all... Vec3d or Vec4d. That's no coincidence; these are useful types that can represent a lot of different kinds of values.
>and FONT with name, size, slant, and ... Most of those attributes seem optional, whereas there aren't really optional parts of a color or orientation. > > Once we give up atomicity and start throwing things together, there's > no logical end to it. And no, that change is *not* needed. I'm not impressed by the "slippery slope" argument. Good programming style always requires good taste. Tim ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
