std::terminate() and std::unexpected()
in [C++]
|
From: wasti.redl on 17 Jun 2008 05:07 On Jun 12, 4:32 am, Martin Bonner <martinfro...(a)yahoo.co.uk> wrote: > On Jun 6, 11:09 pm, wasti.r...(a)gmx.net wrote: > > > Well, VC++ doesn't support set_unexpected. It prints fn2 for a similar > > example using set_terminate, but I haven't tested that one on GCC yet. > > Which version of VC++? VC5 and VC2008 are somewhat differant in how > well they implement the standard. (And yes, there are still people > compiling code with VC5). I use 2003. It ignores exception specifications completely, except for nothrow specifications, which are used for optimization only. (They're mapped onto __declspec(nothrow).) Sebastian -- [ See http://www.gotw.ca/resources/clcm.htm for info about ] [ comp.lang.c++.moderated. First time posters: Do this! ]
From: Erik Wikström on 17 Jun 2008 11:33 On 2008-06-17 22:07, wasti.redl(a)gmx.net wrote: > On Jun 12, 4:32 am, Martin Bonner <martinfro...(a)yahoo.co.uk> wrote: >> On Jun 6, 11:09 pm, wasti.r...(a)gmx.net wrote: >> >> > Well, VC++ doesn't support set_unexpected. It prints fn2 for a similar >> > example using set_terminate, but I haven't tested that one on GCC yet. >> >> Which version of VC++? VC5 and VC2008 are somewhat differant in how >> well they implement the standard. (And yes, there are still people >> compiling code with VC5). > > I use 2003. It ignores exception specifications completely, except for > nothrow specifications, which are used for optimization only. (They're > mapped onto __declspec(nothrow).) Exception specifications is not supported in VC++ (any release) and probably never will, it is not a useful enough feature (i.e. if you start to use a lot exception specifications (other than nothrow) it soon becomes unmanageable). -- Erik Wikstr�m [ See http://www.gotw.ca/resources/clcm.htm for info about ] [ comp.lang.c++.moderated. First time posters: Do this! ]
|
Pages: 1 Prev: Safely redirecting std::cout? Next: Improving ugly(?) design: Data validation |