I have to return to the previous level of the recursion. is the syntax like below right?
void f()
{
// some code here
//
return;
}
I have to return to the previous level of the recursion. is the syntax like below right?
void f()
{
// some code here
//
return;
}
Yes, you can return from a void function.
Interestingly, you can also return void from a void function. For example:
void foo()
{
return void();
}
As expected, this is the same as a plain return;
. It may seem esoteric, but the reason is for template consistency:
template<class T>
T default_value()
{
return T();
}
Here, default_value
returns a default-constructed object of type T, and because of the ability to return void
, it works even when T
= void
.
return void( void() )
is valid also. Code obfuscation contest anyone? –
Merl void foo();
and, in void bar()
, I return foo()
? –
Selfrealization Sure. You just shouldn't be returning an actual value.
Yes, you can use that code to return from the function.
Yes, sometimes you may wish to return void() instead of just nothing.
Consider a void function that wants to call some pass-through void functions without a bunch of if-else.
return
InputEvent == E_Pressed ? Controller->Grip() :
InputEvent == E_Released ? Controller->Release() :
InputEvent == E_Touched ? Controller->Touch() : void();
Yes, that will return from the function to the previous level of recursion. This is going to be very basic explanation, but when you call a function you are creating a new call stack. In a recursive function you are simply adding to that call stack. By returning from a function, whether you return a value or not, you are moving the stack pointer back to the previous function on the stack. It's sort of like a stack of plates. You keep putting plates on it, but than returning moves the top plate.
You could also verify this by using a debugger. Just put a few break points in your code and step through it. You can verify yourself that it works.
The simple answer to this is YES! C++ recognise void method as a function with no return. It basically tells the compiler that whatever happens, once you see the return;
break and leave the method....
You shouldn't have to have the return there, the program will return to the previous function by itself, go into debug mode and step through and you can see it yourself. On the other hand i don't think having a return there will harm the program at all.
As everyone else said, yes you can. In this example, return is not necessary and questionably serves a purpose. I think what you are referring to is an early return in the middle of a function. You can do that too however it is bad programming practice because it leads to complicated control flow (not single-entry single-exit), along with statements like break. Instead, just skip over the remainder of the function using conditionals like if/else().
Yes, for example:
void foo()
{
// do smth
}
and then
void bar(bool condition)
{
if (condition) {
return foo(); //its ok
}
// else do smth
}
© 2022 - 2025 — McMap. All rights reserved.
void main()
is correct that way. – Mvvoid
method, unless it has reference out parameters. – Crabstick