> On the other hand, there are situations where the code is clearer and
> easier to follow if a goto is used. (This is usually where one has to
> do the same exit cleanup should any of a number of tests fail, and in
> finite state machines, I find.) If you think the goto is dirty, rewrite
> your code not to use it and see how dirty it gets. (Well, you know this
> already, or you wouldn't be using the goto.)

I agree.   The remark was tongue in cheek, but it's so hard to detect
such things in email.   :'}

> I think it's time for the rehabilitation of the goto! In fact, perhaps
> I should start a Society for the Rehabilitation of the Goto Statement. :-)

What about the come from?   I really *like* the come from!

			       _MelloN_