Did he think that poor use of pratis comes back to end the function?

Question

I am a developer of PHP and ActionScript, and in some of my functions I use return to end it. Example:

 private function lolsome(a:String):void { if(a == "abs"){return void;} // function code } 

I could just put the function code in its else , but I prefer this way, because in my opinion it is more legible. I just want to know if this is considered bad practice or something like that.

Thanks!

Answer 1

I would only consider this as bad practice if you have returned functions in complex complex functions, because it’s even harder for someone to understand the algorithm when viewing it. However, bad practice is to have large, long functions (they usually should be divided into several smaller functions).

In general, I would consider checking the parameters and the state at the beginning of the function and just go back to good practice, not even quite normal.

But be careful not to clog a function with several different return values ​​in the main logic.

Answer 2

Nope. It's my pleasure. This is often an important element of the control flow, in fact:

 for x in someiterable: if somecondition: return somevalue return None 

This can happen if you repeat a sequence that is looking for something that satisfies a certain condition. If you find something, you will return it and prevent further processing. If you never find it, you will return the default value.

Answer 3

I would not consider this a bad practice. It is widely used.

Answer 4

For further interesting reading, check out “multiple vs single return” on Google. There is a lot of heat. An alternative is usually to keep your return in a condition and only return it once, at the end. Personally, I would prefer to abandon attacks instead of risking that some state changes further along the line; smaller, more focused methods help stop this.

I would say that your practice here is wonderful.

Answer 5

I use it when I'm too lazy to declare a flag and test it. But the fact is that if you use break, return, and such instructions in the middle of your code, you sometimes have to reorganize it when adding functionality.

Therefore, I consider this a bad practice, but it is very often used. Well this is just my opinion: p