This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: ObjC++ Patch Ping, and a question
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Ziemowit Laski <zlaski at apple dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: 13 Sep 2004 19:04:34 +0200
- Subject: Re: ObjC++ Patch Ping, and a question
- Organization: Integrable Solutions
- References: <4C5DE15D-059D-11D9-B47E-00039390FFE2@apple.com>
Ziemowit Laski <zlaski@apple.com> writes:
| http://gcc.gnu.org/ml/gcc-patches/2004-09/msg01176.html
|
| The question is, should I check-in the objcp/ directory while the
| C++ mods are still going in? Originally, I thought I'd postpone this
| until the C++ stuff is done, but questions have arisen (from Gaby
| mostly :-) )
| about how C++ and ObjC++ play together, and it is quite difficult to
| explain without the actual ObjC++ bits at hand.
As you seem to be very confused about what my questions aim at, I have
no interest in the ObjC++ language design. However, I would like to
understand how the C++ front-end relates to your ObjC++ front-end and
why you seem to believe that the way you're modifying the C++
front-end is the way it ought to be without people having to say
anything.
|
| Since ObjC++ will not be built by default, adding objcp/ should not
| perturb the build process (although I shall of course check for this).
|
| Thoughts?
If having objcp/ in place helps you offer meaningful explanation of
why you're modifying C++ front-end the way you do, I'm for it. You'll
however need the RM approval.
-- Gaby