Re: string v.s. basic_string

Hi Larry!

You shouldn't start anything with an underscore in light of 17.4.3.1.2 of the standard (and MSFT's own guidelines regarding identifier names at "file scope").

Of course... I forgot, sorry..

The use of "tstring" also isn't the issue it once was. Unicode is now pervasive enough that most can just rely on "wchar_t" instead. I still find it hard to do that personally however though the "_T()" macro and cousins has always been an eyesore.

It would be nice to have a compiler switch like "/stringliterals_as_unicode", then we could remove all _T macros and L prefixes ;)

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/
.

Relevant Pages

  • Re: string v.s. basic_string
    ... the standard (and MSFT's own guidelines regarding identifier names at "file ... scope"). ...
    (microsoft.public.vc.language)
  • Re: Opinions on "new SomeObject" vs. "SomeObject->new()"
    ... how about some general programming guidelines ... Variables with a broad scope ... Whitespace increases readability. ... an opening indexing bracket or brace, ...
    (comp.lang.perl.misc)
  • Re: types, variable names and fields
    ... No, assuming the same scope, no two typedefs, objects, or functions ... determine what declaration an identifier refers to. ... For structure/union tags and members, ... declarator or type specifier). ...
    (comp.lang.c)
  • Re: Array definition guarantees
    ... linkage tells you where, ... identifier that is spelled sufficiently similarly. ... I think it is closer to say that scope tells you where the name ... The second glitch in this is the "extern" keyword. ...
    (comp.lang.c)
  • Re: Array definition guarantees
    ... linkage tells you where, ... identifier that is spelled sufficiently similarly. ... I think it is closer to say that scope tells you where the name ... The second glitch in this is the "extern" keyword. ...
    (comp.lang.c)