Re: [perl #67912] syswrite prints garbage if called with empty scalar and non-zero offset

On Mon, Jul 27, 2009 at 03:35:02PM +0300, Offer Kaye wrote:
> On Mon, Jul 27, 2009 at 2:02 PM, chromatic wrote:
> >
> > Confirmed in blead.  This looks like a fencepost error.  With the included
> > patch, I get instead an error:
> >
> 
> Maybe we should add a test for this, perhaps in t/op/sysio.t? I
> thought something like the attached patch (not tested).
> 
> Unrelated question - looking at t/op/sysio.t I don't understand, why
> doesn't it use Test::More?

There's a bootstrapping order on tests. The initial tests run avoid relying
on complex constructions such as packages and OO, so that we get clear
failure diagnostics if we introduce a bug that makes them fail.

Nicholas Clark

• [perl #67912] syswrite prints garbage if called with empty scalar and non-zero offset by David Taylor
• Re: [perl #67912] syswrite prints garbage if called with empty scalar and non-zero offset by chromatic
• Re: [perl #67912] syswrite prints garbage if called with empty scalarand non-zero offset by Vincent Pit
• Re: [perl #67912] syswrite prints garbage if called with emptyscalar and non-zero offset by Zefram
• Re: [perl #67912] syswrite prints garbage if called with empty scalar and non-zero offset by Offer Kaye
• Re: [perl #67912] syswrite prints garbage if called with empty scalar and non-zero offset by Nicholas Clark