3 ms·
I was exposed to the "single return" philosophy some time in the mid 80s and for some years I applied it dogmatically to most of my code. However, at some poin
by bborud 16y ago
I was exposed to the "single return" philosophy some time in the mid 80s and for some years I applied it dogmatically to most of my code. However, at some point I started looking at the resulting code and re-evaluating "why am I doing this".
Now, an important point is that I use different languages these days than I did in the 80s. Also, back then I didn't write a lot of (or any?) concurrent/asynchronous code, so the programming style was far more linear and synchronous. The things that applied to my 1980s Pascal or C programs are not necessarily true for my Java/Groovy/C/C++ programs today.