This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Standard header format.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 05 June 2004 22:42, Gabriel Dos Reis wrote:
> "Steven T. Hatton" <hattons@globalsymmetry.com> writes:
> At the time he was writing the book, he knew far more infinitely than
> you seem to believe. In particular, he took care not to write header
> file when he meant "standard header". He even took the specific step
> to tell the reader that users should not have tp know how the standard
> headers are used in implementations.
Actually he said used _by_ the implementations, which in this contex is a
significant difference. I have never suggested he didn't know what he was
talking about. I suspect most implementations did/do provide actual header
files representing the interface to the standard library.
> | Rather than clutter the
> | text with several qualification, he left it stand as an imperfect yet
> | generally useful suggestion. But read what I wrote about my ability to
> | follow that suggestion: "That presents a _minor_ problem for me."
>
> And I told you, you reached a dead end; your insisting does not seem
> to match "_minor_".
What am I insisting on?
> | If you cover it up with an interface,
>
> And we do.
Not in the sense I think of an interface.
interface - a set of declarations that defines how a part of a program can be
accessed.
I can understand that it would probably be difficult to refactor libstdc++ to
provide that interface. If it's too difficult, then say so. If you don't
believe what I'm suggesting would work, then say that. So far the only
argument you've given has been that I don't understand what the Standard
specifies, and that I don't understand a rather vague statement in
TC++PL(SE).
- --
Regards,
Steven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFAwpg1wX61+IL0QsMRAka3AKDpZEAsStKGVl8zdCh8EFyDxBIEdwCg6SqN
ExQCwlIsbkdIB+gpNXgh5fk=
=Ec5S
-----END PGP SIGNATURE-----