Re: [dev] [PATCH][st] Refactor the innermost loop of the xdraws function

From: FRIGN <>
Date: Sat, 7 Jun 2014 11:00:48 +0200

On Fri, 6 Jun 2014 17:12:15 -0700
Charlie Kester <> wrote:

> In fairness to the Java fanatics, prohibitions against goto's predate
> Java by many years. Dijkstra's letter "Go To Statement Considered
> Harmful" was published in 1968, while the Java project wasn't begun
> until 1991.

Still doesn't deny the fact goto has powers you never have with
if-statements. It can be misused (of course), but if handled well, it
is definitely a great tool to handle errors for instance (no need to
call free() in each sub-if-clause but instead "goto fail" and then do
the magic there.

"Go To Statement Considered Harmful" is an interesting approach, but
predates the C-language, too.
Discussing this topic, this is always brought up. I wonder why these
people don't express their own opinion instead and share their magic
ideas why goto is "harmful".

However, I agree with Christoph that this topic and debate are very old.
Let's focus on more relevant stuff instead and do some work ;).



Received on Sat Jun 07 2014 - 11:00:48 CEST

This archive was generated by hypermail 2.3.0 : Sat Jun 07 2014 - 11:12:03 CEST