D: <[EMAIL PROTECTED]>
> Date: Sun, 30 Dec 2007 20:01:42 -0500
> From: Jerry Quinn <[EMAIL PROTECTED]>
> User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20071228)
> MIME-Version: 1.0
> To: Andreas Köhler <[EMAIL PROTECTED]>
> Subject: Re: [patch] More gcc 4.2.3 compila
er-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20071228)
MIME-Version: 1.0
To: Andreas Köhler <[EMAIL PROTECTED]>
Subject: Re: [patch] More gcc 4.2.3 compilation fixes
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
In-Reply-T
Hi,
Am Sonntag, den 30.12.2007, 14:52 -0500 schrieb Jerry Quinn:
> Andreas Köhler wrote:
> > Hi Jerry,
> >
> >> This patch squelches the warnings but I can't help feeling like there
> >> should be a cleaner way of solving the problem.
> >
> > An alternative would be to disable this type of warn
Andreas Köhler wrote:
> Hi Jerry,
>
>> This patch squelches the warnings but I can't help feeling like there
>> should be a cleaner way of solving the problem.
>>
>> Opinions welcome,
>> Jerry Quinn
>
> ---8<--o-->8---
>
> An alternative would be to disable this type of warning completely, like
Hi Jerry,
Am Sonntag, den 30.12.2007, 13:36 -0500 schrieb Jerry Quinn:
> After the last fix, I ran into another set of cases of gcc being too
> smart for its own good. In this case, we're calling the macro
> QOF_BOOK_LOOKUP_ENTITY, which checks its args for null pointers.
> However, several in
Hi again,
After the last fix, I ran into another set of cases of gcc being too
smart for its own good. In this case, we're calling the macro
QOF_BOOK_LOOKUP_ENTITY, which checks its args for null pointers.
However, several indirect callers such as gncInvoiceLookupFlip() and its
siblings are p
