Leopold Toetsch:
# Brent Dax wrote:
# > First of all, spf_render.c:18-20:
# > /* Per Dan's orders, we will not use sprintf if snprintf isn't
# > * around for us.
# > */
# >
# > So we can't use vfprintf, unless Dan thinks otherwise.
#
# Sorry, I don't get that. I see/know the point WR
Brent Dax wrote:
I have issues with this patch.
Leopold Toetsch:
# PIO_eprintf can fallback to vfprintf(3), when no
# interpreter is supplied, which means that we should have compatible
# format chars for basic data types.
First of all, spf_render.c:18-20:
/* Per Dan's orders, we will not
I have issues with this patch.
Leopold Toetsch:
# PIO_eprintf can fallback to vfprintf(3), when no
# interpreter is supplied, which means that we should have compatible
# format chars for basic data types.
First of all, spf_render.c:18-20:
/* Per Dan's orders, we will not use sprintf if s
Simon Glover (via RT) wrote:
# New Ticket Created by Simon Glover
# Please include the string: [perl #23006]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23006 >
At the moment, if you build Parrot with long doubles on
# New Ticket Created by Simon Glover
# Please include the string: [perl #23006]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23006 >
At the moment, if you build Parrot with long doubles on Linux/x86, then
Configure def
