This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Backtrace library [1/3]


On Tue, Sep 11, 2012 at 11:49 PM, Ian Lance Taylor <iant@google.com> wrote:
> On Tue, Sep 11, 2012 at 9:36 PM, Chris Lattner <clattner@apple.com> wrote:
>>
>> On Sep 11, 2012, at 4:24 PM, Ian Lance Taylor <iant@google.com> wrote:
>>
>>> On Tue, Sep 11, 2012 at 4:07 PM, Chris Lattner <clattner@apple.com> wrote:
>>>>
>>>> FYI, "backtrace" is a well-known function provide by glibc (and other libc's).  It might be best to pick another name.
>>>
>>> Good point.  Thanks.  I renamed it to backtrace_full.  I've included
>>> the updated backtrace.h here.  The other changes are mechanical.
>>
>> What do you think of (poor man's) namespacification?  You could prefix symbols with "libbacktrace_", which I think is much less likely to conflict, and be much more clear to clients.
>
> Right now they all begin with "backtrace_".

That is a good choice for a C interface.  I don't think it needs to be longer.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]