This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ Darwin Port BUG in source code
Dale Johannesen <dalej@apple.com> writes:
| On Feb 6, 2005, at 4:01 PM, Gabriel Dos Reis wrote:
|
| > Andrew Pinski <pinskia@physics.uc.edu> writes:
| >
| > | Then we only change one thing and it is easier to make sure that we
| > | got this right
| > | and that the names stay constantly used.
| >
| > and we get two functions supposed to have same or similar semantics
| > and wonder which to call ;-)
|
| To prevent this sort of thing from happening again, I'd like to
| suggest an agreement
| that functions in the language-specific areas of the code have
| language-specific
| names. The ones specific to C++ should begin with cp_, for example.
| Sound OK?
Almost. Currently there are two flavors of pratice in the C++
front-end: either cp_ or cxx_.
Personally, I prefer cxx_ (and find it less ambiguous than cp_) but I can
understand other people feel otherwise.
But I definitely agree that front-end specific routines should be
prefixed by markers that unambiguously identify where they logically
belong to. The trouble is with routines at the front-ends
intersection (e.g. C-C++, C-Objc, C++-Objc++, etc).
-- Gaby