Not if you want to keep your job.
I've used "goto" in C/C++ quite a few times, and I still have a job. ;-)
Actually, while it's a good rule of thumb to avoid "goto" whenever reasonably possible (and most times it *is* reasonably possible) there are always a few times when avoiding one just for the sake of obsessive-compulsion can make the code a lot uglier than it would be otherwise.
Some of the more obvious examples are error-handling (like you're 12 levels deep in control structures and it's time to bail the hell out because of a major failure), or similar special-case scenarios.
In many of those situations, all the goto-less alternatives are even uglier than the more simple and obvious "goto CLEANUP_AND_RETURN;" option.
Actually, while it's a good rule of thumb to avoid "goto" whenever reasonably possible
I agree wholeheartedly. Use of 'goto' should never be 'taken lightly' and should be avoided, except when it's absurd no to use it.t