🚀 go-pugleaf

In article Grv@falcon.daytonoh.attgis.com, Dick Menninger <Dick.Menninger@daytonoh.attgis.com> writes:
>> ==========Steve Clamage, 2/4/96==========
>> 
>> For every person who wants just one more vital feature added to
>> the draft, someone else wants the standard to be declared
>> finished and published. The Committee has decided not to add
>> any more features, and to fix the remaining problems with
>> what we already have.
>
>Since I have been something of a pot sturrer on similar
>issues, it may come as a surprise that I completely endorse
>this stand as the only possible course for the committee.
>The language has not fully grown up, particularly in STL-related
>issues.  Yet it desparately needs to leave home and grow up
>after it does. ...
>
>So, how does growth continue in such a forced, imperfect
>circumstance?  "It will not be in the standard" has to be
>a premise of ANY answer.

Let's take STL hash tables as an example. A rather complete proposal has
been submitted, and some implementations of it currently exist. If it
proves useful, it will be a common extension in implementations.

The Standard goes up for review 5 years after being adopted. (The C
Standard is now undergoing such a review.) At that time, new features
that have enjoyed wide support can be added to the standard. (A
number of new features are likey to be added to C, for example, in the
current round of activities.)

---
Steve Clamage, stephen.clamage@eng.sun.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://reality.sgi.com/employees/austern_mti/std-c++/policy.html
]