This is the mail archive of the
mailing list for the GCC project.
Re: Rename unwind.h to unwind-gcc.h
- From: Ian Lance Taylor <iant at google dot com>
- To: John Marino <gnugcc at marino dot st>
- Cc: Douglas B Rupp <rupp at adacore dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 16 Apr 2014 12:54:05 -0700
- Subject: Re: Rename unwind.h to unwind-gcc.h
- Authentication-results: sourceware.org; auth=none
- References: <534C168F dot 8060400 at adacore dot com> <CAKOQZ8wOqyJp1dEDJAOcZfrq7y2OKtjNsZ8KyUstTYK5Y769gQ at mail dot gmail dot com> <534D1BD1 dot 1080100 at adacore dot com> <CAKOQZ8zQNrvYqJAWE6eRPY_O7K517F5MxW8Ttx+UpCVRtZVGng at mail dot gmail dot com> <534E2ACC dot 5010500 at marino dot st>
On Wed, Apr 16, 2014 at 12:01 AM, John Marino <firstname.lastname@example.org> wrote:
> On 4/16/2014 03:22, Ian Lance Taylor wrote:
>> On Tue, Apr 15, 2014 at 4:45 AM, Douglas B Rupp <email@example.com> wrote:
>>> On 04/14/2014 02:01 PM, Ian Lance Taylor wrote:
>>> No I considered that but I think that number will be very small. Will you
>>> concede, in hindsight, that it would be better had the name been chosen to
>>> be more unique?
>> No, I won't concede that. The unwind.h file provides the interface
>> for the C++ exception handling interface
>> (http://mentorembedded.github.io/cxx-abi/abi-eh.html). That interface
>> is implemented by several different compilers, not just GCC.
> The header can provide the exact same interface with a different, better
> file name.
> He's basically asking, "If you had it to do all over again, would you
> still call it unwind.h or would you call it something different?"
> It's just an academic discussion because answering yes or no changes
> nothing, but I think the majority of the people would give it a
> different file name if they could do it all over again. It's not a big
I agree that it doesn't matter at this date, but I would still vote to
call it unwind.h. It's a good descriptive name for the interface
described by the file. I certainly wouldn't call it unwind-gcc.h;
it's intentionally not GCC-specific.