uncaught_exception() doesn't have a throw specification.

It is intentionnal ? Does it means that one should be prepared
to handle exceptions thrown from uncaught_exception() ?

uncaught_exception() is called in exception handling contexts
where exception safety is very important.

--

Valentin Bonnard                mailto:bonnardv@pratique.fr
info about C++/a propos du C++: http://pages.pratique.fr/~bonnardv/
---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

In article <35C5C973.3E04@pratique.fr>,
  bonnardv@pratique.fr wrote:
> uncaught_exception() doesn't have a throw specification.

Nor is there a remark in the standard about whether it is allowed to throw.

> It is intentionnal ?

It seems highly unlikely that the issue was ever considered.

> Does it means that one should be prepared
> to handle exceptions thrown from uncaught_exception() ?

To be truly portable to all possible standard implementation, I suppose the
answer would be yes. But I would be very surprised if any implementation ever
threw an exception from uncaught_exception(). This should be handled as a
defect in the standard, IMO.

-Dave

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum


[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]