From: "David McClain" <dmcclain@azstarnet.com>
To: <caml-list@inria.fr>
Subject: Oh, how far we HAVEN'T come!
Date: Wed, 8 Nov 2000 18:56:42 -0700 [thread overview]
Message-ID: <000401c049f0$50220780$210148bf@dylan> (raw)
I just received the latest copy of IEEE Computer Magazine - I had to double
check that it was this month's issue and not April! The very back article
about the "profession" was written by Neville Holmes, U. of Tasmania. It is
embarrasing to the point that I hesitate to offer that I am a member of the
IEEE Computer Society.
He starts off alright by talking about the difficulty of producing correct
code in the absense of type checking and syntax error reporting (my
interpretation, not his), and then by the third paragraph when he states
"Much could be done to help programmers avoid such coding errors.", he
totally looses me to the point of anger!
He is concerned about coding conventions such as how to abbreviate
identifiers, and how to match up enclosing braces, and placement of
semicolons....
What an opportunity lost to the ML community. Is this all the further we
have managed to come?
Totally Pissed!!!!
- D.McClain, Sr. Scientist, Raytheon Missile Systems Co., Tucson, AZ
next reply other threads:[~2000-11-09 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 1:56 David McClain [this message]
2000-11-11 16:34 ` John Max Skaller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000401c049f0$50220780$210148bf@dylan' \
--to=dmcclain@azstarnet.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).