[wx-dev] Re: case insensitive find() in wxString

[Jorgen Bodde]

The discussion was that if we introduce more functionality that is not
related to std::string, it will be hard to convert the wxString to
std::string in the future (which Vadim mentioned).

So instead of bloating wxString, take it out and keep it as seperate class.
With advantages that it can be expanded with e.g.

- A parser component (wxStringUtils::PeekChar, wxStringUtils::PopChar,
wxStringUtils::ParseToken)
- More comprehensive routines to generate e.g. a comma seperated list
- Wrapping of text on a certain boundary
- Etc.

The forum is full of wxString things on the Code Dump section, and it might
be a nice alternative to bloating an elementary class.

With regards,
- Jorgen



On 8/2/06, ABX <abx at abx.art.pl> wrote:
>
> "Jorgen Bodde" <jorgen.maillist at gmail.com>:
> > Why not write a wxStringUtils class that can manipulate a wxString class
> by
> > introducing all the functionality that a std::string does not have. This
> way
> > you can extend all you want, but not pollute wxString too much, and it
> can
> > be used on std::string and wxString in the most effective way.
>
> Isn't that close to what we already have named wxStringBase and wxString ?
>
> ABX
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wx-dev-unsubscribe at lists.wxwidgets.org
> For additional commands, e-mail: wx-dev-help at lists.wxwidgets.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wxwidgets.org/pipermail/wx-dev/attachments/20060802/fe00a=
378/attachment.htm