This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
"Encapsulated" exception handling?
- From: Brad Spencer <spencer at infointeractive dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Mon, 26 Apr 2004 17:43:35 -0300
- Subject: "Encapsulated" exception handling?
Here's a general-seeming question, but since it would strike me that
the answer may be implementation-dependent, I'll ask here.
Is exception handling "encapsulated" in that an object file (or shared
library) that catches "all" exceptions can use a different version of
g++ than other exception-using code that calls it? If stack unwinding
never "leaves" the object file (or shared library), do the exception
handling mechanisms of it and its callers have to be "the same"?
I'm not just wondering about gcc-2.95.x vs. gcc-3.x; I'm also
wondering about differences between 3.x versions. Sorry if I'm off
topic.
--
------------------------------------------------------------------
Brad Spencer - spencer@infointeractive.com - "It's quite nice..."
Systems Architect | InfoInterActive Corp. | A Canadian AOL Company