On Fri, Oct 05, 2007 at 05:57:01PM -0400, Josh Sled wrote:
> Christian Stimming <[EMAIL PROTECTED]> writes:
> > Your change, however, is a different expression: With your case, if the
> > char
> > pointer points to a non-empty string, use it, but otherwise use the pointer
> > to an empty string.
On Fri, Oct 05, 2007 at 09:22:53PM +0200, Christian Stimming wrote:
> Am Donnerstag, 4. Oktober 2007 22:56 schrieb Andrew Sackville-West:
> > At jsled's prompting, I'm taking a stab at hacking my way through gcc
> > 4.2.1 (debian) warnings. And, at warlord's oh-so-kind prompting, I'm
> > actually t
Christian Stimming <[EMAIL PROTECTED]> writes:
> Your change, however, is a different expression: With your case, if the char
> pointer points to a non-empty string, use it, but otherwise use the pointer
> to an empty string.
>
> Which points me to the question: Which gcc warning did you try to f
Am Donnerstag, 4. Oktober 2007 22:56 schrieb Andrew Sackville-West:
> At jsled's prompting, I'm taking a stab at hacking my way through gcc
> 4.2.1 (debian) warnings. And, at warlord's oh-so-kind prompting, I'm
> actually trying to do something about them.
Patches are always great! Thanks for pick
At jsled's prompting, I'm taking a stab at hacking my way through gcc
4.2.1 (debian) warnings. And, at warlord's oh-so-kind prompting, I'm
actually trying to do something about them.
All credit for these will likely belong to whichever poor beleaguered
dev happens to be on #gnucash at the moment.
