mrnobo1024 sent the following bits through the ether:
> Parrot_sprintf isn't recognizing 7 as a number in the precision field, so
> trying to use that results in a "'7' is not a valid sprintf format" error.
Thanks, patch applied.
Leon
--
Leon Brocard..
# New Ticket Created by mrnobo1024
# Please include the string: [perl #23005]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23005 >
Parrot_sprintf isn't recognizing 7 as a number in the precision field, so
tryin
Jürgen Bömmels (via RT) wrote:
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #18098]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18098 >
Thanks, applied.
leo
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #18098]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18098 >
Some of the flags Parrot_sprintf functions don't work in the same wa
At 12:25 PM -0700 10/11/02, Brent Dax wrote:
Argh. It looks like all the tests on PPC with the varargs core are
failing, but the test with the PMC core (t/op/string.t #96) isn't. I
don't get it--are they *trying* to make varargs impossible to use?!?
No, that's just a happy side-effect. :)
Da
> Brent, what do you need to help work this out? Is there anyone out
> there who could loan a PPC account to Brent, or perhaps be familiar
> enough with stdarg to take a look directly? (Or how about some
> grizzled grayhair who can tell us if this approach is doomed for
> portability reasons? Not
Brent Dax:
# Can someone with a PPC box try to figure out why this is happening?
#
# /op/string.# Failed test (t/op/string.t at line
# 1224)
# # got: '-1.13014e-302
# # -1.13014e-302
# # '
# # expected: '80.43
# # -1.1
# # '
#
Andy Dougherty:
# On Wed, 9 Oct 2002, Brent Dax wrote:
#
# > Can you try this?
# >
# > (at the top of the function...)
# > va_list *arg = (va_list *) & (obj->data);
# > (vararg accesses should look like...)
# > va_arg(*arg, ...);
# > (no end-of-function assignment should be n
At 9:11 AM -0700 10/11/02, Steve Fink wrote:
>Brent, what do you need to help work this out? Is there anyone out
>there who could loan a PPC account to Brent, or perhaps be familiar
>enough with stdarg to take a look directly? (Or how about some
>grizzled grayhair who can tell us if this approach
On Thu, Oct 10, 2002 at 09:57:01AM -0400, Andy Dougherty wrote:
> On Wed, 9 Oct 2002, Brent Dax wrote:
>
> > Can you try this?
> >
> > (at the top of the function...)
> > va_list *arg = (va_list *) & (obj->data);
> > (vararg accesses should look like...)
> > va_arg(*arg, ...);
>
On Wed, Oct 09, 2002 at 11:28:32PM -0700, Brent Dax wrote:
> Once I clear up the issue with the Sun compiler, I'll be committing
> this. Well, a slightly modified version. Relax, it's nothing
> drastic--I just ran it through check_source_standards.pl and
> run_indent.pl.
That checkin broke the
On Wed, 9 Oct 2002, Nicholas Clark wrote:
> Which reminds me, not sure if this is relevant yet, but there's some or other
> platform that p5p encountered that can't simply copy whatever it is the opaque
> type va_list expands to there.
>
> There's a perl5 Configure symbol need_va_copy which indi
On Wed, 9 Oct 2002, Brent Dax wrote:
> Can you try this?
>
> (at the top of the function...)
> va_list *arg = (va_list *) & (obj->data);
> (vararg accesses should look like...)
> va_arg(*arg, ...);
> (no end-of-function assignment should be necessary)
>
> If that w
Andy Dougherty:
# You'll probably also want the enhanced sprintf tests (or
# something like
# them.) Currently, the only one that fails for me is the
# %5.3f test, which gives 0.500 in stdio, but
# 0.5 from Parrot.
I finally tracked down this bug. If you look,
On Wed, Oct 09, 2002 at 04:42:36PM -0400, Andy Dougherty wrote:
> On Wed, 9 Oct 2002, Andy Dougherty wrote:
>
> > diff -r -u parrot-orig/t/src/sprintf.t parrot-andy/t/src/sprintf.t
>
> > + dval = 1.0e6;
> > + S = Parrot_sprintf_c(interpreter, "== %g\n", dval);
> > +
On Wed, 9 Oct 2002, Andy Dougherty wrote:
> diff -r -u parrot-orig/t/src/sprintf.t parrot-andy/t/src/sprintf.t
> + dval = 1.0e6;
> + S = Parrot_sprintf_c(interpreter, "== %g\n", dval);
> + printf("%g %s", dval, string_to_cstring(interpreter, S));
Aargh. I fo
On Wed, 9 Oct 2002, Andy Dougherty wrote:
> > # Unfortunately, the compact-looking
> > #
> > # ch=va_arg((va_list)obj->data, char);
> > #
> > # gave Sun's compiler indigestion.
> Hmm. Just removing the (va_list) cast makes both Sun's compiler and
> gcc happy. (That's because va_list is
On Wed, 9 Oct 2002, Brent Dax wrote:
> Andy Dougherty:
> # Overall, it continues to look very good. Unfortunately, the
> # compact-looking
> #
> # ch=va_arg((va_list)obj->data, char);
> #
> # gave Sun's compiler indigestion. I had to split it up into
> # the much more pedestrian
> #
>
Andy Dougherty:
# Overall, it continues to look very good. Unfortunately, the
# compact-looking
#
# ch=va_arg((va_list)obj->data, char);
#
# gave Sun's compiler indigestion. I had to split it up into
# the much more pedestrian
#
# va_list arg;
# arg = (va_list) obj->data;
#
On Wed, 9 Oct 2002, Brent Dax wrote:
[Brent continues to churn out amazing quantities of good stuff]
Overall, it continues to look very good. Unfortunately, the compact-looking
ch=va_arg((va_list)obj->data, char);
gave Sun's compiler indigestion. I had to split it up into the much
more p
esterday. One of my long-term goals with Parrot_sprintf was to
use it as the engine for a Parrot bytecode-level sprintf opcode, but I
didn't think that would be possible without duplicating the code in two
different files with different versions of the same macros wrapping
accesses t
Andy Dougherty:
# After just this little patch: (line numbers are off due to
# other unrelated fiddling on my part)
#
# it compiles. So far, I only have seen 2 failed tests:
#
# The first is t/src/sprintf.t, which looks like an off-by-one
# issue of some sort. I haven't tracked it further y
On Tue, 8 Oct 2002, Brent Dax wrote:
> OK. This is a pretty big patch. (Fine--*really* big, at 117K. :^) )
>
> First of all, it completes the feature set of the Parrot_sprintf family,
Thanks!
After just this little patch: (line numbers are off due to other
unrelated fiddling o
At 10:09 PM 12/20/2001 -0800, Brent Dax wrote:
>The attached patch implements a Parrot_sprintf function. It doesn't do
>quite what you think--it just wraps the system sprintf. However, it
>provides I and F sizes and is designed to interact with STRINGs. For
>example:
I'v
The attached patch implements a Parrot_sprintf function. It doesn't do
quite what you think--it just wraps the system sprintf. However, it
provides I and F sizes and is designed to interact with STRINGs. For
example:
FLOATVAL f;
INTVAL i;
STRING
25 matches
Mail list logo
