This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Putting C++ code into gcc front end
- From: Dale Johannesen <dalej at apple dot com>
- To: Marc Espie <espie at quatramaran dot ens dot fr>
- Cc: Dale Johannesen <dalej at apple dot com>, gcc at gcc dot gnu dot org
- Date: Wed, 5 Mar 2003 09:53:53 -0800
- Subject: Re: Putting C++ code into gcc front end
On Wednesday, March 5, 2003, at 08:23 AM, Marc Espie wrote:
In article <6997EA81-4E6A-11D7-80F3-000393D76DAA at apple dot com> you write:
If you really want to be compliant, all external names have to be
unique
within 6 characters, case-insensitive (3.1.2). Somehow I doubt that's
going to happen.
On the contrary, this is really easy to do. Just run nm, cut at six
chars,
look at collisions. Then add an includ at config.h level which
correctly
mangles the names to avoid collisions if wanted.
Actually, I didn't say it wasn't easy to do, I just doubted it would
happen.
(And maintaining your scheme correctly over time seems even less
likely.)
There's no real reason to IMO; long names have been portable (although
not standard) since I started writing in C in the mid-80s. I know of no
current environment that needs this restriction (obviously, none that
gcc currently builds in has it).