Re: changes to T::H to enable continuous testing

2004-02-08 Thread Andy Lester
> Please let me know when you do document the format and make > sure to allow for extensions. I urge you do to so before > the sample size, and divergent extensions, gets too large. Patches are always welcome. Also, I don't see any sample size greater than one on this, unless I'

Re: changes to T::H to enable continuous testing

2004-02-08 Thread Scott Bolte
On Sun, 8 Feb 2004 17:27:02 -0600, Andy Lester wrote: > On Sun, Feb 08, 2004 at 08:41:59AM -0600, Scott Bolte ([EMAIL PROTECTED] > ) wrote: > > I agree, but I still believe it would be good if Test::Harness > > laid out syntax rules for extensions. > > There are no extensions. They're up

Re: changes to T::H to enable continuous testing

2004-02-08 Thread Michael G Schwern
On Sun, Feb 08, 2004 at 05:27:02PM -0600, Andy Lester wrote: > On Sun, Feb 08, 2004 at 08:41:59AM -0600, Scott Bolte ([EMAIL PROTECTED]) wrote: > > I agree, but I still believe it would be good if Test::Harness > > laid out syntax rules for extensions. > > There are no extensions. They're

Re: cvs commit: parrot/docs/resources up.gif

2004-02-08 Thread Michael Scott
On 9 Feb 2004, at 01:49, Nicholas Clark wrote: Have the LZW patents(*) expired everywhere yet google tells me there's one down and seven to go http://www.kuro5hin.org/story/2003/6/19/35919/4079 I just pinched it from parrotcode.org. Does that make me a felon? Mike

Re: cvs commit: parrot/docs/resources up.gif

2004-02-08 Thread Nicholas Clark
On Mon, Feb 09, 2004 at 12:08:25AM -, Mike Scott wrote: > cvsuser 04/02/08 16:08:25 > > Added: docs/resources up.gif > Log: > another image for the docs > > Revision ChangesPath > 1.1 parrot/docs/resources/up.gif > > <> Have the LZW patent

[PATCH] Re: t/src/io failure

2004-02-08 Thread Jeff Clites
On Jan 26, 2004, at 2:00 AM, Leopold Toetsch wrote: Michael Scott <[EMAIL PROTECTED]> wrote: I see that t/src/io is now failing on OS X 10.3.2. Is anyone else seeing this on another system? t/src/iook 12/19# Failed test (t/src/io.t at line 395) # got: '0 # 0 # 0 # ' #

Re: changes to T::H to enable continuous testing

2004-02-08 Thread Andy Lester
On Sun, Feb 08, 2004 at 08:41:59AM -0600, Scott Bolte ([EMAIL PROTECTED]) wrote: > I agree, but I still believe it would be good if Test::Harness > laid out syntax rules for extensions. There are no extensions. They're up to whoever wants to. I'm certainly not going to define arbitra

Re: Keyed Access to UnManagedStruct?

2004-02-08 Thread Leopold Toetsch
Chromatic <[EMAIL PROTECTED]> wrote: > Hi there, > What's the best way to access fields within an UnManagedStruct, one > returned from an NCI call? For example, if I call _new_SDL_Screen, how > can I access the w and h fields of the SDL_Surface it returns? > I've tried creating an OrderedHash ca

Keyed Access to UnManagedStruct?

2004-02-08 Thread chromatic
Hi there, What's the best way to access fields within an UnManagedStruct, one returned from an NCI call? For example, if I call _new_SDL_Screen, how can I access the w and h fields of the SDL_Surface it returns? I've tried creating an OrderedHash called layout and then doing: set screen

Re: changes to T::H to enable continuous testing

2004-02-08 Thread Paul Johnson
On Fri, Feb 06, 2004 at 11:03:42AM -0600, Scott Bolte wrote: > I'd like to propose an addition to the Test::Harness parsing > rules to support dependency analysis. That, in turn, allows > monitoring for file changes and selective, immediate > re-execution of test files. Is

Re: changes to T::H to enable continuous testing

2004-02-08 Thread Scott Bolte
On Fri, 6 Feb 2004 13:34:01 -0800, Michael G Schwern wrote: > > Test::Harness parses 'ok' and 'not ok' and 'Bail out'... Test::* > modules produce the output Test::Harness parses. So your extra logic > to parse "depends on" would go into your Test::Harness extension, but > the depends_on() funct