On Wed, Oct 18, 2006 at 04:10:46PM -0400, Daniel Jacobowitz wrote:
> I'm now worrying that I misunderstood how the gnulib vasnprintf works,
> though. This may be less useful than I thought, since it uses both the
> result of arg parsing and the format string :-(
Never mind, this bit is obviously
On Wed, Oct 18, 2006 at 09:44:58PM +0200, Bruno Haible wrote:
> > > How does what you need compare with the register_printf_function /
> > > parse_printf_format facility in glibc's public header file ?
> >
> > Wow, I knew about register_printf_function, but I'd never noticed
> > parse_printf_form
Daniel Jacobowitz wrote:
> A standard printf. We're not trying to print out new things, we're
> trying to print out standard things using different sorts of arguments.
>
> Here's an example. You can open up GDB and say this:
>
> (gdb) printf "%lld\n", 1
> 1
OK, thanks, I see the intent and the
On Wed, Oct 18, 2006 at 06:08:22PM +0200, Bruno Haible wrote:
> Daniel Jacobowitz wrote:
> > For GDB, we're looking at fixing our printf built in command once and
> > for all. What we really need to do that is two separate interfaces
> > that can talk to each other: one for parsing a format string
Daniel Jacobowitz wrote:
> For GDB, we're looking at fixing our printf built in command once and
> for all. What we really need to do that is two separate interfaces
> that can talk to each other: one for parsing a format string, and one
> for converting arguments.
Do you need a standard printf,
For GDB, we're looking at fixing our printf built in command once and
for all. What we really need to do that is two separate interfaces
that can talk to each other: one for parsing a format string, and one
for converting arguments. Basically, this is printf_parse plus the
rest of vasnprintf, but
