Is there a place that actually describes when it's appropriate to use which
string type, and how to know if we should be "fixing" code we run across?
Is everything just supposed to be string16?
-Albert
On Fri, May 1, 2009 at 11:59 AM, Evan Martin <e...@chromium.org> wrote:
>
> We have a bunch of places where wchar_ts still exist, and none of them
> are correct. I think this isn't particular instance isn't likely to b
> *that* much waste but it definitely would be nice to fix.
>
> I fixed command line switch names to be ASCII on the train into work
> once just 'cause it was bothering me.
>
> On Fri, May 1, 2009 at 11:42 AM, Mike Pinkerton <pinker...@chromium.org>
> wrote:
> >
> > Why are our internal pref keys all wchar_t strings? That's pretty
> > wasteful for something the user never sees and doesn't need to be
> > localized. It's really wasteful on Mac and Linux (32bit wchar_t).
> >
> > Is this on anyone's radar to fix? Should I file a bug?
> >
> > --
> > Mike Pinkerton
> > Mac Weenie
> > pinker...@google.com
> >
> > >
> >
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
