problems with locale.cc

[Gabriel Dos Reis]

Benjamin Kosnik <bkoz@cygnus.com> writes:

| ( Now that I think about this, maybe it would be better to have the
| classname::membername in the changelogs instead of just the membername. )

Ok. That seems to be a sensible way to go: we may have a member foo()
and a non-member foo().

[...]

| > Hmm. A good question. I would be in favor of just (functionY), because you
| > can usually tell from the context of the file what class you are talking
| > about. The additions to the GNU coding standard for C++ in particular are
| > in C++-STYLE, you might want to check this out, although it says nothing
| > about this specific issue.
| 
| I'd go for foo::bar, since it guards against a file then containing two
| different classes that contain `bar'.

Exactly.

-- Gaby