Re: C++ changes

[Roger H. <rog...@mi...>]

> But why you just doesn't declares a new routine that takes the class 
> size instead of the instance size, and add a flag to note what kind of 
> class is it?

Because the extra parameter is only temporary, and in any case I do not 
want to
leave the CVS source in an inconsistent state for a long period whilst 
I check in the
changes to every file to add the extra parameter, and then again when I 
remove it later.



>> 1) Should every E3ClassTree routine be a friend or a method?
>> 2) If a method, then should ones with a TQ3Object take it as their 
>> 'this' ?
>
> I second the James proposal of a class for tree methods

I have found a good solution, the real root class is now E3ClassTree, 
and
OpaqueTQ3Object inherits from it (and currently adds no fields or 
methods).
E3ClassTree currently has lots of friend routines, but these will soon 
be replaced
with methods, though the friend routines will temporarily remain until 
all calls to
them can be changed, but they will just be inline calls to the real 
method anyway.
Hopefully I can get rid of them in a week or two.




>> 3) If so, should the method names be as in option A, B or C ?
>
> IMHO Always whatever makes sense (in your case option C)


Great.


I hope to check in E3ClassTree  on Monday, or later today if there are 
no snags to iron out.