This is the mail archive of the libstdc++@sourceware.cygnus.com mailing list for the libstdc++ project. See the libstdc++ home page for more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
( Now that I think about this, maybe it would be better to have the classname::membername in the changelogs instead of just the membername. ) From: Brendan Kehoe <brendan@cygnus.com> To: Benjamin Kosnik <bkoz@cygnus.com> > * src/basic_file.cc(sys_open) [O_BINARY]: Declare __testb. FYI, to be a perfectionist this would be > * src/basic_file.cc (sys_open) [O_BINARY]: Declare __testb. With a space. :) > > changes. For future reference, should member functions in a > > changelog be listed as (classX::functionY) or just (functionY)? > > 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'. B -- Brendan Kehoe Web page: http://www.zen.org/~brendan/