TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
X-To: Randy Brukardt <[log in to unmask]>
Date: Tue, 18 Jul 2000 14:53:56 -0400
Reply-To: Richard Conn <[log in to unmask]>
From: Richard Conn <[log in to unmask]>
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Parts/Attachments: text/plain (23 lines)

Since my position matches that of the definition quoted by Mike Feldman,
I have no idea why you think it's not supported.  I started off saying
that a standard can be proprietary (which was my point), and Mike disagreed
and then agreed, quoting his definition.

As for your issues, it sounds like you are saying that something cannot
be a standard if it is not clear and unambiguous.  That's not the case
either ... some standards are ambiguous or unclear, as is the English

Richard Conn, Principal Investigator
Reuse Tapestry


Memo to Rick: I've read this whole thread, and I think that most of the
E-Mail supports Mike Feldman's possible. I don't know what mail you read,
but you'd have to twist it a lot to support your position. Perhaps Microsoft
has figured out a way to brainwash attendees to Tech-Ed? :-)