3 ms·
The goal of this article is not to provide some genuine insight to the topic, but to serve as a publicity stunt for the largest code academy in Bulgaria, dubiou
by bluetomcat 9y ago
The goal of this article is not to provide some genuine insight to the topic, but to serve as a publicity stunt for the largest code academy in Bulgaria, dubiously called "Software University". On numerous other occasions their lecturers and trainers have made ridiculously misleading claims about trivial programming stuff. One of their lecturers insisted that the second return in "return; return;" was probably needed just in case the first one did not work:
https://www.youtube.com/watch?v=_ZwiMlyeQNU&t=15s https://www.youtube.com/watch?v=_ZwiMlyeQNU&t=15s
In short, kids with little to no programming experience teach other disorientated desperate kids with few career opportunities in a country with a primitive economy.
- flavio81 9y ago>One of their lecturers insisted that the second return in "return; return;" That guy has a great career ahead in comedy!
- weberc2 9y ago> just in case the first one did not work I repeat all statements in my code for exactly this reason. Sometimes I even compile the same code twice. You can never be too careful.
- Stratoscope 9y agoWell, I'm sorry, but I agree with the lecturer. I've run into this problem myself. In my case I had some cleanup code to run at the end of the function in an error case, so I used "goto fail;" instead of "return;". And then just to be sure it always worked, I put in the "goto fail;" twice!