[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: inlinable functions instead of macros
From: |
Eli Zaretskii |
Subject: |
Re: inlinable functions instead of macros |
Date: |
Sun, 19 Aug 2012 00:03:42 +0300 |
> Date: Sat, 18 Aug 2012 13:57:58 -0700
> From: Paul Eggert <address@hidden>
> Cc: Stefan Monnier <address@hidden>, address@hidden
>
> On 08/18/2012 12:08 PM, Richard Stallman wrote:
> > Could a GCC improvement be a good fix for this? For instance, if it
> > allowed the assertion failure to find and mention the source location
> > of the function's caller?
>
> That could be done via GCC.
What do __FUNCTION__ and __func__ hold for an inlined function?
- Re: inlinable functions instead of macros, (continued)
- Re: inlinable functions instead of macros, Tom Tromey, 2012/08/24
- Re: inlinable functions instead of macros, Paul Eggert, 2012/08/24
- Re: inlinable functions instead of macros, Eli Zaretskii, 2012/08/25
- Re: inlinable functions instead of macros, Tom Tromey, 2012/08/25
- Re: inlinable functions instead of macros, Paul Eggert, 2012/08/26
- Re: inlinable functions instead of macros, Stefan Monnier, 2012/08/24
- Re: inlinable functions instead of macros, Paul Eggert, 2012/08/26
- Re: inlinable functions instead of macros, Eli Zaretskii, 2012/08/22
- Re: inlinable functions instead of macros, Richard Stallman, 2012/08/18
- Re: inlinable functions instead of macros, Florian Weimer, 2012/08/19
- Re: inlinable functions instead of macros, Sam Steingold, 2012/08/20