Article View: comp.std.c++
Article #2817Re: Stuff C++ needs
From: Dick Menninger
Date: Sat, 02 Dec 1995 10:10
Date: Sat, 02 Dec 1995 10:10
55 lines
2650 bytes
2650 bytes
> ==========Matt Austern, 11/30/95========== > The real standardization issue here is that the standard class library > doesn't include any multidimensional array classes; I find that > unfortunate, since multidimensional arrays are widely useful. > Presumably most compiler vendors will provide them, even if the > standard doesn't require them to; maybe we can hope for a de facto > standard version. I have a stronger hope that a committee will form that includes compiler vendor representation for the purpose of establishing a forum for making up front de facto standard additions. Having them agree (rather than war over things that should ultimately end up in the next revision of the real stanard upteen years from now) would benefit all. As far as STL is concerned, there are many things that seem to have missed only because of time. It is incomplete as a result. Some of those would start the effort. Of course, additional stuff would follow including changes (possibly in a distinct namespace) to existing stuff that was found to miss the newly perceived mark. This is needed at minimum. Such a committee could even take on language extensions and fixups so that those have more commonality. If fixing the exception mechanism is seen as new rather than clenaup by the committee, then this would need attention by the less formal forum. It would likely give rise to the defacto language going beyond the standard time-wise, but that seems to be the norm in most standards efforts. Look at SCSI standards for an example of the real world moving faster than the standards process. It can be done. There are probably even better examples out there. But for SCSI standards, the defacto effort seems part of the formal effort, at least during the more recent stages (the earlier stages were more like the war approach). Good Day Dick Dick.Menninger@DaytonOH.ATTGIS.COM --- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu. Contact address: std-c++-request@ncar.ucar.edu. The moderation policy is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
Technical Details
Message-ID:
<DIxDJD.IqM@falcon.daytonoh.attgis.com>Path:
arc1-ca.pugleaf.net!howland.reston.ans.net!agate!agate!MattReferences:
<MATT.95Nov30190005@cyclops5.berkeley.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!howland.reston.ans.net!agate!agate!Matt From: Dick Menninger <Dick.Menninger@daytonoh.attgis.com> Newsgroups: comp.std.c++ Subject: Re: Stuff C++ needs Date: 02 Dec 1995 10:10:48 GMT Organization: AT&T Global Information Solutions Approved: Matt@Austern Message-ID: <DIxDJD.IqM@falcon.daytonoh.attgis.com> References: <MATT.95Nov30190005@cyclops5.berkeley.edu> Reply-To: mennid <Dick.Menninger@daytonoh.attgis.com> NNTP-Posting-Host: austern.hip.berkeley.edu