This is the mail archive of the
mailing list for the GCC project.
Re: RFC: attribute "unpadded"
- From: Joe Buck <Joe dot Buck at synopsys dot com>
- To: fjh at cs dot mu dot OZ dot AU (Fergus Henderson)
- Cc: mark at codesourcery dot com (Mark Mitchell),gcc at gcc dot gnu dot org (gcc at gcc dot gnu dot org)
- Date: Tue, 27 Aug 2002 14:24:56 -0700 (PDT)
- Subject: Re: RFC: attribute "unpadded"
> > People who generate C from their
> > object-oriented language compilers and want C++ interoperability also
> > would like to make use of this feature.
> Wouldn't those people be better off just retargetting their compilers
> to generate C++ rather than C?
It would certainly seem so. After all, we'd be talking about an extension
supported only by GNU C, and anyone who can get GNU C can get GNU C++ for
the same platform. Not only that, but by targeting C++, *any* C++
compiler could be used, not just GNU. Given this, I can't conceive of why
as a tool-maker I'd want to take advantage of such a feature (and writing
tools that generate C or C++ code is what I do for a living).
In the old days, my approach tended to be to generate C, but found that I
wasted a lot of my time duplicating features that C++ provides for free
(reliable constructors and destructors, for example), so it's better to