[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reconciliation of libsnprintfv vs. autogen

From: Daniel Jacobowitz
Subject: Re: Reconciliation of libsnprintfv vs. autogen
Date: Mon, 26 Feb 2007 11:31:18 -0500
User-agent: Mutt/1.5.13 (2006-08-11)

On Mon, Feb 26, 2007 at 08:21:15AM -0800, Bruce Korb wrote:
> > #define PRINTF_ERROR(pi, str) \
> >-        printf_error(pi, __FILE__, __LINE__, SNV_ASSERT_FMT, str);
> >+        printf_error(pi, __FILE__, __LINE__, SNV_ASSERT_FCN, str);
> >
> >That's not defined anywhere.
> It is a function name.  It is supposed to get defined to
> __FUNCTION__ for GCC and empty for anything else.
> It is a configurable.  (Shouldn't it be __FILE__ for anything else?)
> >../../libsnprintfv/snprintfv/printf.c: In function
> >'parse_printf_format':
> >../../libsnprintfv/snprintfv/printf.c:386: error: 'SNV_ASSERT_FCN'
> >undeclared (first use in this function)
> Something is broken in the configury.

In the autogen sources it appears to be named SNV_ASSERT_FCN.  In the
libsnprintfv repository, it's named SNV_ASSERT_FMT - just grep for it.
Which one should it be?  Can't have half and half.

Daniel Jacobowitz

reply via email to

[Prev in Thread] Current Thread [Next in Thread]