Developer Argues For 'Forgotten Code Constructs' Like GOTO and Eval (techbeacon.com)

mikeatTB quotes TechBeacon: Some things in the programming world are so easy to misuse that most people prefer to never use them at all. These are the programming equivalent of a flamethrower... [But] creative use of features such as goto, multiple inheritance, eval, and recursion may be just the right solution for experienced developers when used in the right situation. Is it time to resurrect these four forgotten code constructs?
The article notes that the Linux kernel uses goto statements, and links to Linus Torvalds' defense of them. ("Any if-statement is a goto. As are all structured loops...") And it points out that eval statements are supported by JavaScript, Python, PHP, and Ruby. But when the article describes recursion as "more forgotten than forbidden," it begs the inevitable question. Are you using these "forgotten code constructs" -- and should you be?

Comments

Doing it wrong?

[marc.pn.beaupre]

Honest question: Am I not supposed to use recursion? Am I missing something?

Re:Doing it wrong?

[j_kenpo]

I'm just as baffled by this. I wasn't aware that recursion went out of style. Just another tool in the algorithm and design pattern toolbox. Did I miss the memo that it was taboo as GOTO?

Re: Doing it wrong?

[Anonymous Coward]

Well, most compilers convert most recursions into loops anyway: it is called tail recursion optimization.

Correction: *some* compilers will convert *some specifically structured* tail-recursive function calls into loops.

There are lots of ways to make recursive function calls not tail-calls which renders them ineligible for compiler optimization.