William Perry <wmperry(a)aventail.com> writes in xemacs-beta(a)xemacs.org:
SL Baur wrote:
> Qt uses C++ constructors and
> destructors and thus is impossible to use under the current XEmacs
> architecture.
Why do you say that?
Based on past experiences with egcs/the new gcc. Constructor stuff
can get called before main() and before we have a chance to take any
of our usual precautions. I don't fully understand the technical
details, but it was giving me corrupted memory and when I asked one of
the now-gcc maintainers about how to turn off global constructors,
explaining briefly XEmacs startup & dumping, I was told that dumping
was stupid and deserved to lose.
Do any GUI objects get dumped?
They shouldn't be, but any memory allocation prior to main() can later
cause a coredump.
That's the only thing I could think of that would screw up Qt
(or
any C++ stuff in general). Qt even has an 'Xt' extension now, where
you can mix & match a Qt & an Xt application. They have examples
for 'mainly xt' and 'mainly qt' flavors of apps.
I think mostly-xt would be the easiest way to get it to work under
XEmacs.
Right.