2. If it could be determined which type of object <ph> is
referring
to.
[ All objects deriving from QObject are detected fine but any
other
class does not respect this construct, i.e. QSize and allied
classes ]
You have to use different GC blocks with different destructors for
each
class which do not have common destructor. You can also add 'type'
filed
and try to implement it using single GC destructor function but IMO
it's
not good idea.
I am thinking of separate GC destructor.
However I would like to experiment with "type" field, what is this
and how it will behave? Some small code snippet will be handy.
IMO this would make the code monolithic, so it would indeed
be a (very) bad idea. Using the "type" method you'd have one
central release routine which calls _all_ destructors depending
on object type.
This in practice means that any HBQT based apps would have to
link in the *all* QT classes in final executable. Thus causing
significant bloat.
It's better to simply have them separately, and it's also much
better fits to current code layout. It also makes it easier to
debug.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
