Path: utzoo!mnetor!uunet!husc6!mailrus!nrl-cmf!cmcl2!brl-adm!adm!PEPRBV%CFAAMP.BITNET@husc6.harvard.EDU
From: PEPRBV%CFAAMP.BITNET@husc6.harvard.EDU (Bob Babcock)
Newsgroups: comp.lang.c
Subject: Re: The D Programming Language: cases (fallthrough)
Message-ID: <12159@brl-adm.ARPA>
Date: 6 Mar 88 22:14:10 GMT
Sender: news@brl-adm.ARPA
Lines: 14

>    Almost every language has a goto construct, apparently on the
>principle "We know you won't use goto's, but there might be a special
>case where you need one, so here it is - better to be safe than sorry."
>But do people actually use it to any significant extent?  Why not just
>drop it?

I don't understand.  First you give a perfectly reasonable example of
the use of goto (which would be awkward to code otherwise), and then
you propose eliminating goto from the language because you don't use
it very often.  One of the reasons I like programming in C rather than
(pre-77) Fortran is that you have the flow control constructs
necessary to eliminate abusive use of goto's, but you still have
goto available for the occasional place where it best expresses
what you want to do.