Re: Is the STL too authentic... ?

Thread View: de.comp.lang.c++

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Alexander Ehrler Mon, 02 Oct 1995 05:11

#501

Author: Alexander Ehrler
Date: Mon, 02 Oct 1995 05:11

34 lines
1878 bytes

Andrew Koenig (ark@research.att.com) wrote:
: In article <44kgjg$cuv@nz12.rz.uni-karlsruhe.de> ukci@rzstud1.rz.uni-karlsruhe.de (Alexander Ehrler) writes:

: It is possible to implement safe containers on top of unsafe ones.
: I don't know how to implement fast containers on top of slow ones.
: There is also nothing stopping implementations from providing
: bounds-checked versions of STL if they so desire.


Correct, but I think wether a container handles bound violations or not
is not only a question of implementation. It's important to know if
one can rely on exception handling by the utility classes. Therefore a list
of potentially thrown exceptions is part of a class member's interface.

The second problem is that every software company that provides an ISO C++
compiler has to write their own 'user-friendly' version of the standard
STL containers. This will probably lead to a bunch of different higher-level
classes, a situation we face today. AFAIK is the reason of including  
classlibs in the ISO standard to avoid such a mess.

Is there any problem with supporting fast low-level containers as well as
save containers (probably built on top of the fast ones) in the standard ?


Regards,

Alex


--

       ,,,,,        Alex Ehrler * University of Karlsruhe * Computer Science
      ( 0 @ )       Loetzenerstr. 18   *   D - 76139 Karlsruhe   *   Germany
 --oOO--(_)--OOo--  email: ukci@rz.uni-karlsruhe.de   *  phone: (0721)681609

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads