On Tue, 7 Mar 2006 09:39:31 +0100
Melchior FRANZ <mfranz@...> wrote:
> * Jean-Yves Lefort -- Tuesday 07 March 2006 09:30:
> > Melchior FRANZ <mfranz@...> wrote:
> > > If it can'tbe done cleanly before the release, then we can still [...]
> > What about my solution?
> Oh, true. Still an ugly workaround, but the best of all so far.
It's not an ugly workaround, it's the only clean way to ensure
portability. According to the test page, no standard requires the C++
stack to be unrolled after a cancellation is received. You can see
that the cancellation_exception test is reported to fail on
LinuxThreads, OS X, HP-UX, FreeBSD, Solaris and cygwin.
> BTW: what about the other thread using subsystems (voice, tilemanager)?
> No problems there?
FGVoiceMgr would crash on destruction if you didn't leak _thread
(FGVoiceThread::_mutex would then be destroyed while it is still
locked by wait_for_jobs()).
FGTileLoader would crash if FGGlobals::tile_mgr was destroyed.
> PS: Can you *please* finally stop to send a CC of everything?
> I mean, is it not obvious that I'm subscribed here and=20
> follow the thread?
Netiquette may vary. In the other technical mailing lists I hang on,
people copy eachother. I'll try to remember to make an exception for
you (please do copy me, btw).