Re: func return question

From:

cpp4ever <n2xssvv.g02gfr12930@ntlworld.com>

Newsgroups:

comp.lang.c++

Date:

Wed, 30 Jun 2010 16:37:13 +0100

Message-ID:

<KwJWn.80258$x15.21213@hurricane>

On 06/30/2010 03:50 PM, Pete Becker wrote:

On 2010-06-30 10:12:42 -0400, cpp4ever said:

On 06/30/2010 02:44 PM, Alf P. Steinbach /Usenet wrote:

* AnonMail2005@gmail.com, on 30.06.2010 15:41:

On Jun 30, 9:06 am, "RB"<NoMail@NoSpam> wrote:

I am relatively inexperienced in C++ but trying to learn. I ran
across this
in my studies. My question is not about the declspec since I
understand that
it keeps the prolog and epilog out of the declared function.
My question rather is exactly what is going on with throw( ) .
I.e. is throw
returning the previous function ?
------------------------------------------------
inline __declspec(naked) unsigned __fastcall Xadd(volatile unsigned*
t, int x) throw()
{
__asm mov eax, edx
__asm lock xadd dword ptr [ecx], eax
__asm ret

}

That's an exception spec. This spec says that the function will not
throw any exceptions. If for some reason the function does throw an
exception (or throws an exception that is not specified in the spec),
a predefined function void unexpected() is called. The default action
is to call terminate().

Since the OP is using MSVC: MSVC just ignores exception specifications.

And in C++0x they'll be removed or at least deprecated.

Cheers,

- Alf

Thanks for the info Alf, assuming C++0x, (or should that now be C++1x?),

No, it's C++0x.

has that finalised. For the time being I'll use C++ according to the
latest published standard, around 1998 I believe.

2003.

Exception specifications are deprecated in C++0x. That doesn't mean that
their meaning has changed, nor that you shouldn't use them. It's a
warning that in some future standard they might be removed.

Thanks again, I have that published 2003 standard book. That's not a
feature of C++ I use frequently, and given the C++0x standard
information kindly provided I won't be doing so in future.

cpp4ever