>>27
Yes, you need the goto because C doesn't have high level constructs for exception handling. Isn't that what I said?
>>28
A language shouldn't force a programmer to abandon gotos, and very occasionally an algorithm can be expressed more elegantly with a goto somewhere, but normally when you feel the need to use a goto, something is wrong.
Of course structured programming shouldn't be overdone. When I write in Pascal, having to use the Result variable leads to lots of nested ifs in complex code, whereas things are much clearer in C with the return keyword.