[c++] bug 2628 and new

[Gabriel Dos Reis]

Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr> writes:

| [1  <text/plain; us-ascii (7bit)>]
| 
| 
| gdr@codesourcery.com said:
| > | 3) we could issue a diagnostic when -fno-exceptions is enabled an 
| > | operator new is called (and any other throw expression?)
| 
| > A pedwarn? 
| 
| I'd say that the solution should also work for the other situations 
| (at least dynamic_cast on reference can throw).

I forgot that one.  Thanks for the remind.  What should happen in
effect?   
But I suspect code which enables -fno-exceptions won't use
dynamic_cast<> on references (if not by perversion :-)

Does it worth adding a special case for non-standard use of 
dynamic_cast<> ? Jason ?

-- Gaby
CodeSourcery, LLC                       http://www.codesourcery.com