Hi Mark, > This is not an ABI issue; the presence of absence of an > exception-specifier does not affect the ABI.
Yes, I realized in the meanwhile, via my usual layman investigations using nm. [snip explanation] Ok. Actually I can clearly remember when you advertised the use of throw() whenever possible... Now, however, I'm not sure to understand which kind of way forward you can see... Should the warning machinery be smart enough to not warn at all in this case? Or? Sorry, probably it's just my ignorance about those issues at the interface between core and library, I would really appreciate a bit of additional guidance. Paolo.
