Re: Testing Inline::C

2004-02-11 Thread Andrew Savige
Michael G Schwern <[EMAIL PROTECTED]> wrote: > To catch memory mistakes in C, I'd normally use something like Electric > Fence or other malloc replacement. Basically something that replaces the > memory allocation functions with those that put in magic so that if your > program walks outside its a

Distributed testing idea

2004-02-11 Thread Michael G Schwern
The biggest time suck in developing MakeMaker, and to a lesser extent Test::More, is running the tests. Why? Because they need to be run on lots of different platforms with lots of different versions of Perl. Currently, I do this by hand. And we all know manual testing sucks. Its time consuming

Re: Testing Inline::C

2004-02-11 Thread Michael G Schwern
On Wed, Feb 11, 2004 at 08:50:03AM -0800, Ovid wrote: > I've a problem in testing Inline::C. In the module > AI::NeuralNet::Simple, I do some work allocating and deallocating > memory and I've been bitten by a bug where I wasn't allocating memory > properly for one of my arrays. It's fixed, but

Re: GNU Aegis help wanted.

2004-02-11 Thread Tony Bowden
On Tue, Feb 10, 2004 at 06:41:00PM -0800, Michael G Schwern wrote: > Trouble is, I haven't used Aegis since 2001 and never in such a distributed > environment and never played with aedist or maintained the repository. > So I could use some help. At this point I'd just like to know who out > there

Testing Inline::C

2004-02-11 Thread Ovid
Hi all, http://search.cpan.org/~ovid/AI-NeuralNet-Simple-0.02/ I've a problem in testing Inline::C. In the module AI::NeuralNet::Simple, I do some work allocating and deallocating memory and I've been bitten by a bug where I wasn't allocating memory properly for one of my arrays. It's fixed, b