This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Standard header format.


"Steven T. Hatton" <hattons@globalsymmetry.com> writes:

| 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 

<quote>
   In general, implementers use standard headers in ways programmers
   cannot predict and shouldn't have to know about
</quote>

| significant difference. I have never suggested he didn't know what he was 
| talking about.

You did:

#                                                     I believe Stroustrup was 
# operating under the traditional assumption that the standard headers are in 
# fact header files.  I do believe that's what he meant.

when I told you that he was aware of variosu schemes used by implementers.

[...]

| > | If you cover it up with an interface,
| >
| > And we do.
| 
| Not in the sense I think of an interface. 

Then, you've reached another dead end.

| interface - a set of declarations that defines how a part of a program can be 
| accessed.

An interface need not excusively consist in declarations.  It may 
consist in directives too.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]