QUESA_OBJECTS_ARE_OPAQUE

[Dair G. <da...@re...>]

Hi,

I've been discussing some performance improvements with Roger off-list:
we have a couple of different approaches, but the common factor is to
make the definition of TQ3Object be opaque even within Quesa itself.

This then gives us the freedom to change how general object behaviour
happens - if the rest of the code goes through a function to get at
state, we can experiment with changes to how objects are structured
without disturbing existing code.

I've started checking in the first bits of this: you should not notice
any changes in behaviour, but there's a temporary build constant to help
this transition (QUESA_OBJECTS_ARE_OPAQUE).

That is off by default - currently turning it on will produce a lot of
build failures, but I plan to go through checking in fixes for these and
then eventually remove QUESA_OBJECTS_ARE_OPAQUE once the implementation
is hidden from callers.


-dair (in retrospect that's how it should have been from the start: I
knew it should have been, but thought "ah, that'll never change"... :-)
___________________________________________________
mailto:dair+refnum.com       http://www.refnum.com/