469,950 Members | 1,881 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,950 developers. It's quick & easy.

"void Method()" vs "void Method(void)"

Hello,

I would like to know if there is a difference in c++ between the
following two method-declarations:

void Method();

and

void Method(void);
I know there is a difference in C (the first case means the function may
have parameters, but they are not yet defined?).
But how is the semantik in C++? Is there a difference or are both
declarations equal in _every_ case?

I would be glad to get an answer to this question (and perhaps a
reference where this topic is explained (C++-standard?)).

Regards
ollej
Jul 23 '05 #1
7 2363

"Ollej Reemt" <ol***@gmx.de> wrote in message
news:d4********@news.Informatik.Uni-Oldenburg.DE...
Hello,

I would like to know if there is a difference in c++ between the
following two method-declarations:

void Method();

and

void Method(void);


They are same. Former is the preferred type in C++. Reference to the
Standard --

8.3.5/2 - "...If the parameter-declaration-clause is empty, the function
takes no arguments. The parameter list (void) is equivalent to the empty
parameter list."

Sharad
Jul 23 '05 #2
Ollej Reemt wrote:
Hello,

I would like to know if there is a difference in c++ between the
following two method-declarations:

void Method();

and

void Method(void);
I know there is a difference in C (the first case means the function may
have parameters, but they are not yet defined?).
But how is the semantik in C++? Is there a difference or are both
declarations equal in _every_ case?

I would be glad to get an answer to this question (and perhaps a
reference where this topic is explained (C++-standard?)).

Regards
ollej


In addition to Sharad's reply, I prefer the latter method since
it is explicit and works in both languages.

--
Thomas Matthews

C++ newsgroup welcome message:
http://www.slack.net/~shiva/welcome.txt
C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.learn.c-c++ faq:
http://www.comeaucomputing.com/learn/faq/
Other sites:
http://www.josuttis.com -- C++ STL Library book
http://www.sgi.com/tech/stl -- Standard Template Library
Jul 23 '05 #3
Hello Sharad and Thomas,

thanks for your answers, that was exactly what I wanted to know.

Regards
ollej
Jul 23 '05 #4
Thomas Matthews wrote:
I know there is a difference in C (the first case means the function may
have parameters, but they are not yet defined?).
But how is the semantik in C++? Is there a difference or are both
declarations equal in _every_ case?

I would be glad to get an answer to this question (and perhaps a
reference where this topic is explained (C++-standard?)).

Regards
ollej


In addition to Sharad's reply, I prefer the latter method since
it is explicit and works in both languages.


The point about it working in both languages is valid - if you make a header
that is supposed to be used in both languages, but how is it explicit?
IMHO, if you want to say "no parameters", the most explicit way to describe
that is by putting no parameters between the parens, not by putting a fake
parameter of type void there.

Jul 23 '05 #5
Rolf Magnus wrote:
Thomas Matthews wrote:
I know there is a difference in C (the first case means the
function may have parameters, but they are not yet defined?).
But how is the semantik in C++? Is there a difference or are both
declarations equal in _every_ case?

I would be glad to get an answer to this question (and perhaps a
reference where this topic is explained (C++-standard?)).

Regards
ollej


In addition to Sharad's reply, I prefer the latter method since
it is explicit and works in both languages.


The point about it working in both languages is valid - if you make a
header that is supposed to be used in both languages, but how is it
explicit? IMHO, if you want to say "no parameters", the most explicit
way to describe that is by putting no parameters between the parens,
not by putting a fake parameter of type void there.


I believe 'explicit' in this case refers to what Ollej originally said:
in C, an empty parameter list does not necessarily mean that the
function takes no arguments. In a header file shared between C and C++
code, foo(void) will *explicitly* tell either language that foo takes
no arguments. Writing foo() will only explicitly say that to C++ code.

Kristo

Jul 23 '05 #6
Kristo wrote:
Rolf Magnus wrote:
Thomas Matthews wrote:

I know there is a difference in C (the first case means the
function may have parameters, but they are not yet defined?).
But how is the semantik in C++? Is there a difference or are both
declarations equal in _every_ case?

I would be glad to get an answer to this question (and perhaps a
reference where this topic is explained (C++-standard?)).

Regards
ollej

In addition to Sharad's reply, I prefer the latter method since
it is explicit and works in both languages.


The point about it working in both languages is valid - if you make a
header that is supposed to be used in both languages, but how is it
explicit? IMHO, if you want to say "no parameters", the most explicit
way to describe that is by putting no parameters between the parens,
not by putting a fake parameter of type void there.

I believe 'explicit' in this case refers to what Ollej originally said:
in C, an empty parameter list does not necessarily mean that the
function takes no arguments. In a header file shared between C and C++
code, foo(void) will *explicitly* tell either language that foo takes
no arguments. Writing foo() will only explicitly say that to C++ code.


And what Rolf said is still true: in English having something to designate
nothing is the source of confusion. Haven't you seen (in the Standard, no
less) pages, where the only _content_ is "this page is left intentionally
blank". Isn't it a self-contradictory statement? That's what "explicitly
emtpy argument list" means in C++: no arguments, nothing between the
opening parenthesis and the closing one. I actually strongly agree with
Rolf on this one. To be _explicit_, one should simply have bare parens.

V
Jul 23 '05 #7
On Wed, 20 Apr 2005 14:43:57 -0400, Victor Bazarov
<v.********@comAcast.net> wrote in comp.lang.c++:
Kristo wrote:
Rolf Magnus wrote:
Thomas Matthews wrote:
>I know there is a difference in C (the first case means the
>function may have parameters, but they are not yet defined?).
>But how is the semantik in C++? Is there a difference or are both
>declarations equal in _every_ case?
>
>I would be glad to get an answer to this question (and perhaps a
>reference where this topic is explained (C++-standard?)).
>
>Regards
>ollej

In addition to Sharad's reply, I prefer the latter method since
it is explicit and works in both languages.

The point about it working in both languages is valid - if you make a
header that is supposed to be used in both languages, but how is it
explicit? IMHO, if you want to say "no parameters", the most explicit
way to describe that is by putting no parameters between the parens,
not by putting a fake parameter of type void there.

I believe 'explicit' in this case refers to what Ollej originally said:
in C, an empty parameter list does not necessarily mean that the
function takes no arguments. In a header file shared between C and C++
code, foo(void) will *explicitly* tell either language that foo takes
no arguments. Writing foo() will only explicitly say that to C++ code.


And what Rolf said is still true: in English having something to designate
nothing is the source of confusion. Haven't you seen (in the Standard, no
less) pages, where the only _content_ is "this page is left intentionally
blank". Isn't it a self-contradictory statement? That's what "explicitly
emtpy argument list" means in C++: no arguments, nothing between the
opening parenthesis and the closing one. I actually strongly agree with
Rolf on this one. To be _explicit_, one should simply have bare parens.

V


Once upon a time, I wrote the users manual for a product. I generated
some of the illustrations from AutoCAD drawings of some of the
mechanical parts. As a joke, I created one drawing of a part cracked
in half to go along with the text warning the user about doing
something that could cause damage.

The powers that be saw it, decided it was funny, and wanted it in the
manual. Then at the very last minute, they changed their mind and
wanted it out.

So when the manual was printed, it had several of those pages that
said "this page intentionally blank", and one page, the one that had
held that particular illustration, that said "this page
unintentionally left blank."

Nobody ever noticed.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html
Jul 23 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

188 posts views Thread by infobahn | last post: by
7 posts views Thread by sunglo | last post: by
7 posts views Thread by =?Utf-8?B?cmFtbzk5NDE=?= | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.