🚀 go-pugleaf

X-Original-Date: Tue, 09 Jan 1996 10:22:25 +0200

In article <4crabd$91f@netlab.cs.rpi.edu>, kanze@gabi-soft.fr (J. Kanze) wrote:

>> |> The design of the exception classes has changed since Plauger's book was
>> |> written, and class "exception" no longer has a member function "raise".
>> |> The exception classes now have only
>> |>      default constructor
>> |>      copy constructor
>> |>      assignment operator
>> |>      virtual destructor
>> |>      virtual function "const char* what() const;"
>> 
>> |> The "what" function returns an implementation-defined null-terminated
>> |> character string.

I would suggest that it will return a :

typeid(*this).name() 

as the standard default behavior. This way we don't add another global
string to  the executable's data area, and we re-use the already existing
string ( which represents the name of the exception ).

>> Does this include the constructors?  I don't see where this is stated in
>> the draft, and as most of the constructors (except bad_alloc and
>> bad_exception) take a reference to a string, I would expect them to
>> invoke the copy constructor for string, which I presume *can* throw
>> bad_alloc.

I believe that the string class would best implememnted as a
copy-on-change class, which means that the copy-constructor will not
actually duplicate the string but will increase the reference counter it
uses.

- -- 
- -- Etay Bogner,
- -- Etay_Bogner@mail.stil.scitex.com,
- -- Scitex Corp.
- -- Israel.

    [ comp.lang.c++.moderated is a moderated newsgroup.  Submit articles ]
    [  to <c++-submit@netlab.cs.rpi.edu>.  The moderation policy can be  ]
    [   retrieved from <http://netlab.cs.rpi.edu/~cppmods/guide.html>.   ]
    [    Moderators can be reached at: c++-request@netlab.cs.rpi.edu.    ]