|
From: Frank V. C. <fr...@co...> - 2000-10-16 03:21:27
|
On a back and forth discussion with C., we jived about storage and type derivations. Needless to say, it became apparent that with data member specification enabled in macros for MetaType access, the solution over storage and semantics disolved. I bring to attention the semantics of Numbers, Integers, and RealNumbers Number Integer ShortInteger RealNumber is the new class hierarchy (and the MetaType ontology follows this). So Integer isA Number, ShortInteger isA Integer and they have no semantic association with RealNumber other then being a Number. For the accessor/mutator and storage issue: Integer defines a 32 bit signed value (theValue) ShortInteger accessor/mutator coerces a short in and out using the get/set macros with the extension of re-using the base classes storage area. This is all checked in. Thoughts? PS: To build the 0.2.1 version I have tagged it rel-0-2-1. The above changes are 0.2.2 bound (as yet not tagged). -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |