On Tue, 1 Oct 2002, Brent Dax wrote:
Andy Dougherty:
# *elbows him in the side and points at
# /Parrot_v?sn?printf(_[sc])?/ in
# misc.c*
#
# Interesting, yes, that's mostly what I had in mind, but I'm
# unsure just how it's intended to be used.[*] That is, if I have
#
# INTVAL
Andy Dougherty:
# Here's a patch that makes misc.c work that way. (This does not fix the
# original trace.c problem at the beginning of this thread.
# trace.c still
# needs to be patched. My original patch is fine for now.)
#
# Also, would it be ok to add some more wrapper functions to
#
On Mon, 7 Oct 2002, Brent Dax wrote:
I'm working on a patch locally that fixes the long problem (by testing
at Configure-time for the existence of long long), completes the
feature set of Parrot_sprintf and friends, and adds a PIO_printf and
PIO_fprintf. It also converts most uses of
On Mon, 30 Sep 2002, Brent Dax wrote:
Andy Dougherty:
# More generally, though, rather than sprinkling the sources
# with INTVAL_FMT and other ugly (but correct and portable
# things), should we be trying to
# funnel everything through a central printf-like engine and
# have it
Andy Dougherty:
# *elbows him in the side and points at
# /Parrot_v?sn?printf(_[sc])?/ in
# misc.c*
#
# Interesting, yes, that's mostly what I had in mind, but I'm
# unsure just how it's intended to be used.[*] That is, if I have
#
# INTVAL iv = 7;
#
# what format do I use to print
