From 2785245598554059072 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,307cbe6f0ea2ccd3 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 2003-06-13 11:55:08 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.uchicago.edu!logbridge.uoregon.edu!kibo.news.demon.net!mutlu.news.demon.net!demon!mail2news.demon.co.uk!devnull From: Michiel.Salters@cmg.nl (Michiel Salters) Newsgroups: comp.std.c++ Subject: Re: Recommendation to the Standards Committee Date: Fri, 13 Jun 2003 18:55:07 +0000 (UTC) Organization: http://groups.google.com/ Lines: 38 Approved: fjh@cs.mu.oz.au (Fergus Henderson , moderator of comp.std.c++) Message-ID: References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: mail2news.demon.co.uk 1055530507 10724 10.0.0.1 (13 Jun 2003 18:55:07 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Fri, 13 Jun 2003 18:55:07 +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 19QthZ-0002mp-00 for mail2news@news.news.demon.net; Fri, 13 Jun 2003 18:55:06 +0000 X-Received: from localhost (localhost [[UNIX: localhost]]) by mulga.cs.mu.OZ.AU id EAA08388; Sat, 14 Jun 2003 04:55:01 +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-NNTP-Posting-Date: 13 Jun 2003 13:03:40 GMT X-Spam-Status: No, hits=-12.3 required=5.0 tests=NOSPAM_INC,QUOTED_EMAIL_TEXT,REFERENCES, SIGNATURE_SHORT_DENSE,SPAM_PHRASE_02_03 version=2.41 Xref: archiver1.google.com comp.std.c++:19705 bplummer@hotmail.com ("Brian Plummer") wrote in message news:... > >> 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..." In fact, it could be phrased a lot easier like: Header shall define symbol __HDR_X where X is one of the following [Table] Even where system headers aren't files preprocessor symbols can be defined. This is required for e.g. If these are used as include guards on such no-header-file systems, the effect is the same as on normal systems - no effect except for although compile times can be different. Still, is it worth the trouble? Regards, -- Michiel Salters --- [ 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 ]