TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Thu, 5 Oct 2000 19:23:04 +0300
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
What is your problem? You can also read things like this further down ...

<snip>
Avoid coding in Abundance, or using any of its principles kludged into other
languages. It was designed from the ground up with the primary goal of
making the maintenance programmer's job easier. Similarly avoid Eiffel or
Ada since they were designed to catch bugs before a program goes into
production.
</snip>

It is actually excellent training material! I use a similar list together
with actual examples from "living" code. I call it
Mr-Henssels-Red-Hot-Ears-We-Newer-Do-That-Again-Training.

/soren
Soren Henssel-Rasmussen
Software Quality Engineer
Nokia Mobile Phones, R&D Copenhagen
[log in to unmask]


|Colin Paul Gloster <[log in to unmask]> wrote:
|
| Well who's this!? I was reading some of a website on how to write
| unmaintainable code ("How to Write Unmaintainable Code",
| HTTP://mindprod.com/unmain.html) and found this:
|
| "2.Avoid Ada: About 20% of these techniques can't be used in Ada. Refuse
| to use Ada. If your manager presses you, insist that no-one else uses it,
| and point out that it doesn't work with your large suite of tools like
lint and plummer
| that work around C's failings."

ATOM RSS1 RSS2