Re: checking a loop execution

[Robert Dewar <robert_dewar@my-deja.com>]

In article <3901fc68.0@silver.truman.edu>,
  "Chad R. Meiners" <crmeiners@hotmail.com> wrote:
> Find it amusing that you attach these jokes in reply to my
> posting given that they bear no relevance what so ever since I
> am clearly not allergic to gotos.  So clearly there is no
> reason to go on a crusade.


Sorry, you misunderstood in taking my comments personally, I
was not the least implying what you think about gotos, I have
no idea, and no way of knowing, I was just making general
comments about people's attitudes in general, using the
example you gave as a starting point. The "you" in my message
was not Chad :-) it was just a general comment to those who
get a sick feeling in their stomache when they see a goto.
If you are not one of those, the "you" does not apply!

The "crusade" is a useful one, because the programming field
is afflicted with people who don't really understand principles
and try to replace them with simple absolute rules. These
absolute rules are almost always detrimental (I won't say
always, because then that would be a self referential
criticism :-)

P.S. You ask for substantiantion that I find something
obfuscatory. Hard to give, since this is most certainly a
subjective reaction. The statement is 100% true (that is,
I definitely find the use of boolean variables to represent
control state in this way unnecessarily confusing, and almost
always prefer to restate things so that control state is
represented by the instruction pointer location as nature
intended :-)


Sent via Deja.com http://www.deja.com/
Before you buy.