throw ()

[Mike Harrold]

> 
> On Aug 30, 2000, Mike Harrold <mharrold@cas.org> wrote:
> 
> > This would be the appropriate behaviour (it is unexpected, after all).
> > But is this what "throw ()" actually defines? or what it implies?
> 
> That's the correct behavior of a function declared with throw().

A non-answer if ever I saw one :-)

> 
> > Assuming "throw ()" defines no expcetions, I'd also like to see a
> > warning for the following scenario:
> 
> Yep.  Contributions are welcome :-)

I only wish I knew where to start :-(

/Mike