Re: [boost] [General] Always treat std::strings as UTF-8

Subject: Re: [boost] [General] Always treat std::strings as UTF-8
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2011-01-21 09:01:10

Alexander Lamaison wrote:
>
> Rule 35 of C++ Coding Standard by Sutter and Alexandrescu:
> "Avoid inheriting from classes that were not designed to be
> classes"
 ^
  base

> "Using a standalone class as a base is a serious design error"
>
> The reasons given include undefined behaviour when deleting a
> std::string* pointing to an instance of the subclass, slicing
> if extra data is added and pointlessness as the subclass
> doesn't get any more access to the superclass's implementation
> that it would have had if it just kept std::string as a
> member.

If there are no additional members, then slicing and failure to invoke the derivate's destructor cause no problems, while inheritance means the base class interface needn't be duplicated.  In this case, one gets a new type name that behaves just like std::string at the cost of some forwarding constructors and assignment operators (for the right return type).

That said, following Rule 35 is generally wise.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.