Re: Standard header format.

["Steven T. Hatton" <hattons at globalsymmetry dot com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 08 June 2004 13:24, Phil Edwards wrote:
> On Tue, Jun 08, 2004 at 09:32:24AM -0400, Steven T. Hatton wrote:
> > On Tuesday 08 June 2004 01:57, llewelly@xmission.com wrote:
> > > If the above is intended to inform programmers as the the interface of
> > >     the library, it belongs in the *documentation*, not in the header
> > >     files. Most programmers only look at the header files when the
> > >     documentation is woefully inadequate.
> >
> > I haven't taken a scientific poll, but my experience has been most C++
> > programmers with whom I have discussed this issue have been been quite
> > forceful in stating their belief that header files should present the API
> > to the user, and that should serve as a human readable reference for the
> > user of the API.
>
> And yet, none of those programmers have ever tried implementing a C++
> standard library as portable as this one.

First off, you don't know who these people are, or what they have done.  Some 
of them have significant accomplishment to point to.  

> The ones who /have/ implemented such a library have spent the last few
> days telling you that it doesn't work like that.
>
> Perhaps some observations and tentative conclusions could be drawn from
> this pattern?  Hmmmm...

Yes.  You do not understand what has actually been written.  Furthermore, I 
presented supporting evidence for my position which included the API 
documentation and header files from some of the largest C++ projects in the 
world, and showed the clear correspondence between the header file and API 
documentation.  You failed to address that in the least.
- -- 
Regards,
Steven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAxf5owX61+IL0QsMRAu0BAKC5M1KasGWbtKiQafdtbmkLJN01jACeON8t
8FElW2UGW4eBrN0b9sFUIIk=
=ngn/
-----END PGP SIGNATURE-----