returns in parenthesis

[Bill Cunningham]

What is the difference in return statements in parenthesis and not. I've
never used return(); I've never had a problem with a return statement. My
compiler is C99 too and there is *no* C11 to it. Are they slow on these?

Bill

 

[Bill Cunningham]

"return" statements in parentheses are illegal. Examples:

(return);
(return
(return 0);
(return 0

are all illegal.

I'm sorry. I misspoke. It's return and then a statement in () and it
also doesn't have to be in (). I've never used () and just wordered what it
meant. i.e.

return (TRUE);

When I said /are they slow on these/ I was speaking of being slow to get the
C11 compatible compilers out.

Bill

 

[Siri Cruz]

What is the difference in return statements in parenthesis and not. I've
never used return(); I've never had a problem with a return statement. My
compiler is C99 too and there is *no* C11 to it. Are they slow on these?

Similar looking statements like if(), while(), for() do have mandatory
parenthesis, so sometimes we just unconsciously add them to return on analogy.
It doesn't help anything, but it doesn't hurt either.

 

[Ben Bacarisse]

Similar looking statements like if(), while(), for() do have mandatory
parenthesis, so sometimes we just unconsciously add them to return on
analogy.

And Very Old C insisted on them -- a syntax inherited from B. They were
optional before K&R was first published, but it took me a while to stop
using them as I'd learned B before C.

 

[Bill Cunningham]

And Very Old C insisted on them -- a syntax inherited from B. They
were optional before K&R was first published, but it took me a while
to stop using them as I'd learned B before C.

You've been around this for a very long time. No wonder you are such an
expert.

Bill

 

[Keith Thompson]

What is the difference in return statements in parenthesis and not. I've
never used return(); I've never had a problem with a return statement. My
compiler is C99 too and there is *no* C11 to it. Are they slow on these?

The syntax of a return statement is:

return expression(opt) ;

For a return statement returning a value, parentheses around
expression harmless but are never necessary. (In my humble opinion
adding optional parentheses is poor style because they make the
return statement look like a function call, which it isn't.)

Parentheses are allowed because an expression in parentheses is a valid
expression, exactly equivalent in type, value, and other characteristics
to the unparenthesized expression. There is no reason for performance
to vary depending on the presence or absence of parentheses.

For a return statement that doesn't return a value (used in a void
function):

return;

parentheses are illegal:

return(); /* syntax error */

This has nothing to do with C99 or C11. In the 1975 version of the C
Reference manual, parentheses were required for a return statement with
an expression. I *think* that they were dropped in the 1978 first
edition of K&R (I'll have to check later).

 

[Bill Cunningham]

Keith Thompson wrote:
[snip]

For a return statement returning a value, parentheses around
expression harmless but are never necessary.

[snip]

I thought C was always return a value. Or is that *pass* by value. If
there's a difference.

Bill

 

[Mark Storkamp]

Good to see your trolling is going strong Bill!

7/10.

c.l.c feeding the trolls

10/10.

 

[osmium]

c.l.c feeding the trolls

10/10.

11/10