Standard header format.

Steven T. Hatton hattons@globalsymmetry.com
Wed Jun 9 00:23:00 GMT 2004


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

On Tuesday 08 June 2004 14:33, Matt Austern wrote:
> On Jun 8, 2004, at 10:58 AM, Steven T. Hatton wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----

> > 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.
>
> Unfortunately, I believe that this discussion is at a dead and and that
> it no
> longer serves any useful purpose.
>
> The people who actually implement libstdc++ have explained their reasons
> for using implementation techniques that makes the libstdc++ headers
> less
> transparent to novices and that make it look less immediately like the
> set of
> declarations in the standard.  Whether or not you think those reasons
> are
> valid, the people who do the work think so.

If anything, this part of the discussion has moved off topic here.  There are 
two closely related issues.  Standard Headers and header files. libstdc++ 
implements the Standard Headers. These headers have their origin in the 
concept of header files from C, but are not required to be implemented as 
header files, per se.  Everything I wrote in the above quoted message was 
addressing the use of header files in C++ applications, and not Standard 
Headers.

> If you'd like, you can consider this to be a sign of our incompetence:
> we
> aren't smart enough to see how to achieve all of the other design goals
> while also writing a library in a form that's suitable as a pedagogical
> introduction.  The important thing for you to realize: that isn't going
> to
> change just by your telling us that having a library like that would be
> nice.

You've completely missed the point. If you want to understand what I was 
actually getting at, read my previous posts.

- -- 
Regards,
Steven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAxlkCwX61+IL0QsMRAvD0AKDLActAap37plxBV/GdGZTEgg+E6QCdF4fy
8rMaM6V7z5EfO9uStl9+7v8=
=e/ZO
-----END PGP SIGNATURE-----



More information about the Libstdc++ mailing list