[guappa]

goto was only bad when used to save code and jump indiscriminately. To handle errors is no problem at all.

[froh]

yes, yes, yes! see the Linux Kernel for plenty of such good and readable uses of go-to, considered useful: "on error, jump there in the cleanup sequence ..."

[_flux]

..as long as you don't make mistakes. I fixed enough goto bugs in Xorg when I was fixing Coverity-issues in Xorg that I can see the downsides of this easy way of error handling.

[guappa]

We're comparing to go here, not with a language with proper error handling.