void return

Hello..

Is it smart to return; when void ends?

For instance:

Code:

void somefunction() {
  dosomething();
  return;
}

It's not smart. It's kinda like giving an answer when not being asked. It's the type of thing that puts you into trouble in the army.

However, in C++ the return statement is ignored. No error issued, but may give you a gentle warning... which is always good.

return with no return value is absolutely proper way to exit void function

Didn't even notice the absence of a value. However, are you sure Vart? I always was lead to believe the proper way was to not use the return statement.

No error issued, but may give you a gentle warning... which is always good.

A warning would be strange, since a return statement without an expression used in a function that does not return a value is legal according to the C++ Standard.

Originally Posted by Mario F.

Didn't even notice the absence of a value. However, are you sure Vart? I always was lead to believe the proper way was to not use the return statement.

yes, I'm sure
http://msdn2.microsoft.com/en-us/library/k68ktdwf.aspx

Look at the two examples

Code:

void functionA ( void )
{
   cout << "Red is hot";
}

Code:

void funcionB ( void )
{
   cout << "Yellow is gold";

   return;
  
   cout << "Opps, returned above this cant be read\n";
}

The first is ok, as is the second use of return. A void function that takes no
parameters and returns no value like the two above give the programmer the
"option" to use return without a value to exit the function. If, like iin the second example, any statement is written under the return, it will not be read. As I am sure you are aware, using return is the proper way to exit a function and return to its caller ie: main. Void functions can have no return statement, like the first example. and like mario suggested, this is perfecly ok too. Usually, if or if not the programmer chooses to add a return statement is a personal preference. Many texts teach to use return to end a void function, although leaving it out makes little difference, as the program will automaticly end the function at the closing brace.

Well, ok. But...

When the flow of control exits the block enclosing the function definition, the result is the same as it would be if a return statement with no expression had been executed. This is illegal for functions that are declared as returning a value.

Proper way would be standard enforced. And the standard does not enforce it. It states it can or cannot be used on the case of void functions.

if the return; is the last statement in the void function you can freely avoid it...

but in most cases it is useful in cases like:

Code:

void str_cpy(char* a, char* b)
{
   if(a == b) return; //nothing to do

//here goes the work
}

Absolutely. On that I agree.

Vart is your avatar somthing to do with the film the sixth sense?

Originally Posted by swgh

Vart is your avatar somthing to do with the film the sixth sense?

yes, something to do

Cool. Good film, I like M Nightshalymans films. Yoi cant beat unbreakable though for suspense

It's not necessary to use a return statement before the closing brace of the definition of main() either - if it reaches the end without seeing a return statement, it returns 0 automatically.

At best it returns void. Not 0.