Re: Request for Info Regarding Frightening Problems

[nuchat!shell!pern!rgh@uunet.uu.net (Richard G. Hash)]

>>>>...Aside from all other problems inherent with Ada, which are many
>>>>and frightening...
>>>
>>>Could you list those problems? Especially the frightening ones?
>>
>>Often in the vacinity of a particularly dangerous passageway or near
>>some narrow channel through which ships must pass, or in waterways in
>>which dangerous tides are liable to drive ships into rocks or other
>>hidden obstructions, there will be a warning beacon of some sort; some
>>kind of a repeated signal to prevent the unwary from coming to harm.
>>
>>In similar vein, I have prepared the following little selection of horror
>>stories, to post to this group and on other similar forums once in a while
>>as a similar warning to those whose projects are in danger of cracking up
>>on the shoals of Ada.
>
>   <much deleted>
>   <horrendous Holden horror histories>
>
>Great Scott!! And all this time I've been happily sailing along, writing
>successful Ada code in blissful ignorance of its impossibility. After
>reading this post, I feel like the proverbial bumblebee who's just been
>told he can't fly.

For those of you who subscribe to comp.lang.c++, and who see 150+ daily
posts along the lines of "How does blurfl work?", "Why doesn't <pick some
feature> work?", "Why do I get a segmentation fault when I <sneeze>?",
"How come this works under <vendor A> but won't compile under <vendor B>",
ad nauseum, you have already quickly realized that Teds post was intended
for April 1, but his itchy fingers couldn't wait.

Ted's been predicting gloom and despair for years, and telling us all
how everything we're doing in Ada is a dismal failure, and it will
never work. Despite Mr. Holdens expert opinion our successes indicate
otherwise.

The "frightening" thing is that someone out just might have listened to him.
Gee Ted, I've almost missed you.

-- 
Richard G. Hash    Shell Bellaire Research Center   (713) 245-7311
E-Mail: rgh@shell.com            or   rgh@shell.uucp
    or  rgh%shell.uucp@sun.com   or   rgh%shell.uucp@rice.edu
    or  ...!{sun,bcm,rice,psuvax1,decwrl,cs.utexas.edu}!shell!rgh