signature

[Tony Johansson]

Hello !!
I do know that the name and the parameter are includet in a methode
signature but what abot the return type are then also includet in the
signature.

//Tony

[Ioannis Vranos]

Tony Johansson wrote:

Hello !!
I do know that the name and the parameter are includet in a methode
signature but what abot the return type are then also includet in the
signature.

When we are talking in general, we usually consider the return type to be part of the
function signature.

When we are talking about function overloading specifically, the return type does not
matter on which function will be called.

--
Ioannis Vranos

http://www23.brinkster.com/noicys

[Karl Heinz Buchegger]

Tony Johansson wrote:

Hello !!

I do know that the name and the parameter are includet in a methode
signature but what abot the return type are then also includet in the
signature.

No.

--
Karl Heinz Buchegger
kb******@gascad.at

[Jaspreet]

Tony Johansson wrote:

Hello !!
I do know that the name and the parameter are includet in a methode
signature but what abot the return type are then also includet in the signature.

//Tony

I guess you are talking in reference to function overloading. If that
is so then the return type is ir-relevant. The number or type of
arguments should be different for functions to be overloaded.

There is something called function prototype which is of the form:
return_type function_name (arguments);

Not sure though what your context is..

[MJ]

Hi
You can not overload the function based on the return type, even though
the return type is included in the signature
MJ

[Rolf Magnus]

MJ wrote:

Hi
You can not overload the function based on the return type, even though
the return type is included in the signature

From the C++ standard:

1.3.10 signature defns.signature]
the information about a function that participates in overload resolution
(13.3): the types of its parameters and, if the function is a class member,
the cv- qualifiers (if any) on the function itself and the class in which
the member function is declared.2) The signature of a template function
specialization includes the types of its template arguments (14.5.5.1).

[...]

2) Function signatures do not include return type, because that does not
participate in overload resolution.

[Ioannis Vranos]

Rolf Magnus wrote:

From the C++ standard:

1.3.10 signature defns.signature]
the information about a function that participates in overload resolution
(13.3): the types of its parameters and, if the function is a class member,
the cv- qualifiers (if any) on the function itself and the class in which
the member function is declared.2) The signature of a template function
specialization includes the types of its template arguments (14.5.5.1).

[...]

2) Function signatures do not include return type, because that does not
participate in overload resolution.

However return types are taken under consideration when using pointers to functions.
--
Ioannis Vranos

http://www23.brinkster.com/noicys

[Ron Natalie]

Ioannis Vranos wrote:

However return types are taken under consideration when using pointers
to functions.

That's because the return type is part of the function TYPE. When you
declare a pointer to function, you're declaring a pointer to some
function type.

SIGNATURE is the stuff that applies to overloading (as posted earlier).
The return type is not a factor in overloading.

While people frequently intermix TYPE and SIGNATURE in conversation,
they are not the same thing.

[Ioannis Vranos]

Ron Natalie wrote:

That's because the return type is part of the function TYPE. When you
declare a pointer to function, you're declaring a pointer to some
function type.

SIGNATURE is the stuff that applies to overloading (as posted earlier).
The return type is not a factor in overloading.

While people frequently intermix TYPE and SIGNATURE in conversation,
they are not the same thing.

Interesting. Thanks for the clarification. :-)
--
Ioannis Vranos

http://www23.brinkster.com/noicys

[Ron Natalie]

Ron Natalie wrote:

Ioannis Vranos wrote:

However return types are taken under consideration when using pointers
to functions.

That's because the return type is part of the function TYPE. When you
declare a pointer to function, you're declaring a pointer to some
function type.

SIGNATURE is the stuff that applies to overloading (as posted earlier).
The return type is not a factor in overloading.

While people frequently intermix TYPE and SIGNATURE in conversation,
they are not the same thing.

I should further point out that the SIGNATURE includes the name of
the function (along with the types of the arguments) where as the
type does not include the name.