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: Scope of specifier extern
    ... But none of them have scope; ... The keyword "extern" affects ... The "scope" concept answers the question "can I `see' that identifier ... The "linkage" concept ...
    (comp.lang.c)
  • Re: Is "scope" different from "visibility" ?
    ... The standard does not specifically define "visibility" but it ... Within the inner scope, the identifier designates the entity ... context disambiguates uses that refer to different entities. ...
    (comp.lang.c)