From 3035707603475609696 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,307cbe6f0ea2ccd3 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 2003-06-11 18:19:04 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!kibo.news.demon.net!mutlu.news.demon.net!demon!mail2news.demon.co.uk!devnull From: bplummer@hotmail.com ("Brian Plummer") Newsgroups: comp.std.c++ Subject: Re: Recommendation to the Standards Committee Date: Thu, 12 Jun 2003 01:19:03 +0000 (UTC) Organization: Road Runner - NYC Lines: 50 Approved: fjh@cs.mu.oz.au (Fergus Henderson , moderator of comp.std.c++) Message-ID: References: X-Trace: mail2news.demon.co.uk 1055380743 409 10.0.0.1 (12 Jun 2003 01:19:03 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Thu, 12 Jun 2003 01:19:03 +0000 (UTC) X-Received: from mulga.cs.mu.oz.au ([128.250.1.22]) by news.demon.co.uk with esmtp (Exim 4.12) id 19QGk2-00006Q-00 for mail2news@news.news.demon.net; Thu, 12 Jun 2003 01:19:02 +0000 X-Received: by mulga.cs.mu.OZ.AU id LAA12924; Thu, 12 Jun 2003 11:18:59 +1000 (EST) X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f X-Path: comp-std-cpp-robomod!not-for-mail X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-Delivered-To: std-c++@ucar.edu X-Newsgroups: comp.std.c++ X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-NNTP-Posting-Date: Wed, 11 Jun 2003 21:10:38 EDT X-Spamscanner: mailbox5.ucsd.edu (v1.2 May 26 2003 01:55:38, 1.2/5.0 2.55) X-MailScanner: PASSED (v1.2.7 33858 h5C1Fdgs034285 mailbox5.ucsd.edu) X-Spam-Status: No, hits=-4.5 required=5.0 tests=FORGED_HOTMAIL_RCVD,INVALID_MSGID,NOSPAM_INC, PRIORITY_NO_NAME,QUOTED_EMAIL_TEXT,REFERENCES, SPAM_PHRASE_03_05 version=2.41 Xref: archiver1.google.com comp.std.c++:19699 >> Doesn't seem likely. There is no requirement that the standard >> headers even be implemented as files in the first place. Makes perfect sense. Whilst this may be true, all of the C++ implementations that I use (5 total) all implement most, if not all, of the of the standard library as files. (please note that I only checked iostream and amongst these 5, all implemented iostream as a file). Given this, couldn't we at least make a recommendation in the standard that "if you do implement the standard library include "files" as actual files then the include guards in this file should take the form of blah, blah, blah..." If this step was taken and in thoses cases where the the standard library was implemented as files, this standardization combined with the external header guards that I described in my original post would/could save significant amounts of compile time without any introduction of other "sophisticated" features that may or may not be found in "modern" C++ compilers. Brian "Andrew Koenig" wrote in message news:yu997k7swza8.fsf@europa.research.att.com... > Brian> I have the following recommendation for an addition to the C++ > Brian> standard: I'd like to see the text used for the header guards > Brian> in the standard library header files, well, standardized. > > Doesn't seem likely. There is no requirement that the standard > headers even be implemented as files in the first place. > > -- > Andrew Koenig, ark@research.att.com, http://www.research.att.com/info/ark > > --- > [ comp.std.c++ is moderated. To submit articles, try just posting with ] > [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] > [ --- Please see the FAQ before posting. --- ] > [ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html ] > --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html ]