GOTO is evil, plain and simple
Not true.
Seriously though you can always write code better without it.
Also not true, and it depends on what you mean by "better". If by "better" you mean any of "more readable", "faster" or "more efficient" then there are many cases where not using goto will result in "worse" code.
There's a good discussion on this in the lkml (Linux kernel mailing list) archive from 2003. http://kerneltrap.org/node/553/2131
In this particular case, goto shouldn't be used, and it's initial use reflects the O.P.'s inexperience and that's fine, but making unilateral statements about a language feature that is useful in a small subset of problems is unhelpful. A better rule is "don't use goto unless you have exhausted all other language features and goto still looks better"