home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!taumet!steve
- From: steve@taumet.com (Steve Clamage)
- Subject: Re: Speed, Correctness, Availability, and the Real World
- Message-ID: <1992Jul21.165323.10185@taumet.com>
- Organization: TauMetric Corporation
- References: <23167@alice.att.com> <1992Jul16.180843.26353@microsoft.com> <23209@alice.att.com> <1992Jul20.193413.19944@microsoft.com>
- Date: Tue, 21 Jul 1992 16:53:23 GMT
- Lines: 39
-
- jimad@microsoft.com (Jim Adcock) writes:
-
- >I also would suggest that if the committee feels overwhelmed by the number
- >of suggestions coming in, then the first activities the committee should
- >"chop" are work-items that the committee has made for itself out of whole
- >cloth -- items that don't exist anywhere in written-down form.
-
- I don't believe there are any such work items.
-
-
- >IE some of the "standard" libraries suggestions.
- >If some committee member or non-
- >member thinks that some library that hasn't anywhere been written should
- >be part of the "standard" then such person should *start* by writing such
- >a library, and then write up a proposal for such a library's inclusion.
-
- That is exactly the procedure which has been followed. Nothing is being
- considered for the standard library which does not exist as a written
- proposal (with an implementation). When a member or non-member suggests
- something new, he or she is requested to write it up. No written
- proposal, no consideration.
-
-
- >Note that there is no hard-and-fast reason why such new libraries *have*
- >to be part of the C++ *langauge* standard -- such new libraries are perfect
- >candidates to be factored *out* of the C++ *language* standard to be handled
- >as separate standardization efforts in their own right, when the time comes.
-
- I in fact argued this point at the early C++ Committee meetings. I
- challenged every statement of the form "of course class X must be in the
- standard library." The overwhelming majority of the committee wanted
- some standard classes. So far, only IOstreams and some sort of String
- class(es) are certain to be in the standard library. A generic dynamic
- array class will probably be in the library. A bitset class has been
- proposed and discussed for some time, and might be adopted in some form.
- --
-
- Steve Clamage, TauMetric Corp, steve@taumet.com
- Vice Chair, ANSI C++ Committee, X3J16
-