On Thursday 14 July 2005 10:27, Chris Cannam wrote: > > We used to have a rule not to throw across Qt library boundaries because Qt > might be compiled without exception support enabled. It's maybe still > worth following that one, although I think the justification is history.
The justification was that the exception support of g++ was adding a fairly large overhead, and compiling Qt without it would save quite a few megs of RAM. Apparently this is no longer the case, however I'm not sure how an exception would be handled when thrown across the signal/slot mechanism for instance (emitting a signal which calls a slot which throws). This would certainly be a major headache, so it's probably a good idea to avoid throwing from a slot. -- Guillaume. http://www.telegraph-road.org ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
