At the risk of wading in too deep... there is one aspect of exception
specification checking that I've become absolutely convinced would
benefit greatly from static checking:
A::~A() static throw(); // or whatever syntax
That is, there is some code that you know should not throw anything,
James Dennett wrote:
There has been much debate, and a large fraction of those
involved feel that static checking of exceptions in C++ is
*not* an improvement from the current situation. There
has also been much written on the weaknesses of the Java
approach.
Note: I'm not expressing my person
Bob Rossi wrote:
> On Sun, Jan 14, 2007 at 12:16:32AM -0500, Andrew Pinski wrote:
>>> Hi,
>>>
>>> Will g++ ever add a compile time enforcement of the exception
>>> specification like the Java compiler does?
>>>
>>> I find the exception specification almost useless with out this
>>> functionality.
>
On Sun, Jan 14, 2007 at 12:16:32AM -0500, Andrew Pinski wrote:
> >
> > Hi,
> >
> > Will g++ ever add a compile time enforcement of the exception
> > specification like the Java compiler does?
> >
> > I find the exception specification almost useless with out this
> > functionality.
>
> The C++
>
> Hi,
>
> Will g++ ever add a compile time enforcement of the exception
> specification like the Java compiler does?
>
> I find the exception specification almost useless with out this
> functionality.
The C++ standard ( 15.4/10) is very specific that the implemantion should not
reject code
Hi,
Will g++ ever add a compile time enforcement of the exception
specification like the Java compiler does?
I find the exception specification almost useless with out this
functionality.
Thanks,
Bob Rossi
