[perl #55196] [BUG] print/say opcodes have different float precision

2008-09-09 Thread NotFound via RT
> This falls under the I/O PDD, the next milestone. Hold for a couple of > days. I've added it to the tasklist for the milestone: The print and say opcodes had already been changed some weeks ago, now both call PIO_printf on INT and NUM. By the way, now FLOATVAL_FMT is used instead of "%f"

Re: [perl #55196] [BUG] print/say opcodes have different float precision

2008-09-08 Thread Allison Randal
Christoph Otto via RT wrote: I'll sign up to do the grunt work to fix the failing tests if someone makes a decision on what the consistent behavior should be. This falls under the I/O PDD, the next milestone. Hold for a couple of days. I've added it to the tasklist for the milestone: http

[perl #55196] [BUG] print/say opcodes have different float precision

2008-09-06 Thread Christoph Otto via RT
On Mon Jun 02 13:08:27 2008, [EMAIL PROTECTED] wrote: > On Monday 02 June 2008 12:27:17 Bernhard Schmalhofer wrote: > > > The behavior of > > > > .sub main > > > > $N0 = 3.14159 > > say $N0 > > print $N0 > > print "\n" > > .end > > > > surprised me, as I got: > > > > > > [EMAIL PROTECTED]: