TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show HTML 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: Tom Moran <[log in to unmask]>
Date: Mon, 17 Jul 2000 23:06:26 -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 (34 lines)
The thing I go by is the MSDN Library.  Now, if you think a
standard has to be perfect and unambiguous, your first problem
is that you must write it in a language that is not subject
to interpretation, and English is not that language.

Richard Conn, Principal Investigator
Reuse Tapestry

-----Original Message-----
From: Team Ada: Ada Advocacy Issues (83 & 95)
[mailto:[log in to unmask]]On Behalf Of Tom Moran
Sent: Monday, July 17, 2000 8:38 PM
To: [log in to unmask]
Subject: Re: Standards

>Clearly defined and agreed-upon conventions for programming
>intefaces. Standards may be (bullets mine)

  Can someone please point me to the clearly defined standards for the
Windows API?  I have only some of the definitions in the various books
I have, in the VC++ help files, and in MS's online support, and some
of those definitions do not match reality.  For instance, what is the
standard floating point length mode (64 vs 80 bits) when running under
Windows, and if one particular setting is not part of the spec, then
is it specified to be specific to, and saved and restored for, a
  There's also the little problem of change every few years with new
versions of Windows.