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
Condense Mail Headers

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

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
X-To:
Date:
Fri, 16 Feb 2001 14:53:22 -0500
Reply-To:
Michael Feldman <[log in to unmask]>
Subject:
From:
Michael Feldman <[log in to unmask]>
Content-Transfer-Encoding:
7bit
In-Reply-To:
<"B668ZYWHDZDSY*/R=FBDCVD/R=A1/U=MCCABE JOHN/"@MHS> from "[log in to unmask]" at Feb 14, 2001 09:38:51 AM
Content-Type:
text/plain; charset=us-ascii
MIME-Version:
1.0
Parts/Attachments:
text/plain (27 lines)
[said John]

> I guess the point I'm trying to make is that I don't believe Pascal to be a good
> example of failure in the validation system due to the limited nature of the
> language itself.
>
> John
>
Just a clarification: as I recall, the fellow responsible for the Pascal
validation suite made it clear that Borland Pascal failed in the part of
the language that was covered by the standard, not (just) in the extensions.

The main reason I mentioned it at all was to show the connection between
one Borland statement (we won't do Ada because of validation) and
another Borland position (we don;t even care about Pascal validation -
we'll do as we choose).

It's hard to castigate Borland too much - after all, their customers
didn't care. I'm sure that if Borland could've seen a significant
market for a _validated_ Pascal compiler (say, one with a pragma to
let the user specify ISO compliance, as some C compilers do) they
would've built one.

The same goes for an Ada compiler. Businesses go where the money is.

Mike

ATOM RSS1 RSS2