Alexander Graf writes:
> On 22.02.2013, at 18:41, Andreas Färber wrote:
>
>> Am 22.02.2013 17:54, schrieb Richard Henderson:
>>> On 02/22/2013 08:16 AM, Andreas Färber wrote:
I would be willing to do a macro-based v3 using do { ... } while (0) if
maintainers can reach agreement on that
On 22.02.2013, at 18:41, Andreas Färber wrote:
> Am 22.02.2013 17:54, schrieb Richard Henderson:
>> On 02/22/2013 08:16 AM, Andreas Färber wrote:
>>> I would be willing to do a macro-based v3 using do { ... } while (0) if
>>> maintainers can reach agreement on that and on how to do the if (0).
>>
Hi All,
On Sat, Feb 23, 2013 at 3:41 AM, Andreas Färber wrote:
> Am 22.02.2013 17:54, schrieb Richard Henderson:
>> On 02/22/2013 08:16 AM, Andreas Färber wrote:
>>> I would be willing to do a macro-based v3 using do { ... } while (0) if
>>> maintainers can reach agreement on that and on how to d
Am 22.02.2013 17:54, schrieb Richard Henderson:
> On 02/22/2013 08:16 AM, Andreas Färber wrote:
>> I would be willing to do a macro-based v3 using do { ... } while (0) if
>> maintainers can reach agreement on that and on how to do the if (0).
>
> FWIW, I'm in favor of the
>
> #ifndef DEBUG
> # de
Richard Henderson writes:
> On 02/22/2013 08:16 AM, Andreas Färber wrote:
>> I would be willing to do a macro-based v3 using do { ... } while (0) if
>> maintainers can reach agreement on that and on how to do the if (0).
>
> FWIW, I'm in favor of the
>
> #ifndef DEBUG
> # define DEBUG 0
> #endif
On 02/22/2013 08:16 AM, Andreas Färber wrote:
> I would be willing to do a macro-based v3 using do { ... } while (0) if
> maintainers can reach agreement on that and on how to do the if (0).
FWIW, I'm in favor of the
#ifndef DEBUG
# define DEBUG 0
#endif
#define MACRO_NAME(...) \
do { if (DEBUG
Andreas Färber writes:
> Am 21.02.2013 17:10, schrieb Richard Henderson:
>> On 2013-02-20 20:24, Andreas Färber wrote:
>>> v2 replaces macros with static functions, adopting Scott's scheme of
>>> const
>>> variables set through #ifdefs (keeping their defined() semantics) and
>>> adopting
>>> Anth
Am 22.02.2013 17:00, schrieb Markus Armbruster:
> Andreas Färber writes:
>
>> Am 21.02.2013 17:10, schrieb Richard Henderson:
>>> On 2013-02-20 20:24, Andreas Färber wrote:
v2 replaces macros with static functions, adopting Scott's scheme of
const
variables set through #ifdefs (kee
Am 21.02.2013 17:10, schrieb Richard Henderson:
> On 2013-02-20 20:24, Andreas Färber wrote:
>> v2 replaces macros with static functions, adopting Scott's scheme of
>> const
>> variables set through #ifdefs (keeping their defined() semantics) and
>> adopting
>> Anthony's proposal of using va_list f
Il 21/02/2013 17:10, Richard Henderson ha scritto:
>> v2 replaces macros with static functions, adopting Scott's scheme of
>> const
>> variables set through #ifdefs (keeping their defined() semantics) and
>> adopting
>> Anthony's proposal of using va_list for argument passing.
>> v1 had changed som
On 2013-02-20 20:24, Andreas Färber wrote:
v2 replaces macros with static functions, adopting Scott's scheme of const
variables set through #ifdefs (keeping their defined() semantics) and adopting
Anthony's proposal of using va_list for argument passing.
v1 had changed some #ifdefs into ifs due t
Hello,
Based on suggestions from Igor Mitsyanko, Anthony and Alex this series aims to
expose debug output to compile-testing, so that it doesn't constantly break.
The basic requirement is to move format strings and arguments out of
#ifdef sections or no-op macros, so that the C compiler sees and c
12 matches
Mail list logo
