On Mon, Dec 8, 2008 at 8:09 PM, Brett Wilson <[EMAIL PROTECTED]> wrote:
> Be careful because wstring != UTF16String. > Yes, hence the need to be very explicit about what these functions actually do (since you can't infer things from types alone). In other places of the code, we use GetWString, which if you're > returning a wstring, I think is the best naming convention (since > wstring changes type depending on the platform). It changes type, but does it also change encoding? Basically, all I really want is for us to be as clear as possible. If the only guarantee is that the function will return a "wstring" (but it doesn't guarantee the encoding), then we should make that clear in the names/documentation. Same with the narrow version. PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
