[haiku-development] Re: BString on GCC4
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 20 Apr 2008 15:37:19 +0200 CEST
Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> I suppose we should rather get rid of the non-const version
> completely and
> introduce a SetByteAt[Unchecked]() or something like this. Since
> BStringRef
> is not inline, the operator call is unnecessarily expensive.
+1 - with GCC 4, we don't need to maintain source or binary
compatibility in this regard, so I'm in favour of dropping it, too.
Bye,
Axel.
- References:
- [haiku-development] Re: BString on GCC4
- From: Ingo Weinhold
Other related posts:
- » [haiku-development] BString on GCC4
- » [haiku-development] Re: BString on GCC4
- » [haiku-development] Re: BString on GCC4
- [haiku-development] Re: BString on GCC4
- From: Ingo Weinhold