Re: getting round Test::More test formatting trickiness

2006-03-15 Thread Smylers
Dr Bean writes: > I've gotten comfortable with Test::More conventions, but it's > difficult in my editor to really quickly create lots of tests. Which editor is that? > is($o->index('You'), 1, 'objects index 1'); > isnt($o->index(1), 1, 'objects index 2'); > isnt($o->index(2), 2, 'objects index

Re: Activestate and Scalar-List-Utils

2006-03-15 Thread demerphq
On 3/14/06, Jan Dubois <[EMAIL PROTECTED]> wrote: > On Tue, 14 Mar 2006, David Golden wrote: > > Steve Peters wrote: > > > The problem was that newer Scalar-List-Utils uses an internal Perl > > > function that Windows does not see as an exported function. This was > > > changed with Perl 5.8.8. Onc

Re: getting round Test::More test formatting trickiness

2006-03-15 Thread A. Pagaltzis
* Smylers <[EMAIL PROTECTED]> [2006-03-15 09:05]: >If your editor happens to be Vim then be aware that Ctrl+A adds >1 to the number currently under the cursor, or the next number >on the current line if the cursor isn't on a number. It also has “visual block mode,” which is initiated using Ctrl-v,

Re: Activestate and Scalar-List-Utils

2006-03-15 Thread Adam Kennedy
The main reason this is hapenning is that it's not currently possible to update CORE packages in ActivePerl, so any module that depends on a CORE package can be suffering from this. This problem will persist until it becomes possible to update core packages in ActivePerl. It's certainly not an id

Re: getting round Test::More test formatting trickiness

2006-03-15 Thread Tels
Moin, On Tuesday 14 March 2006 10:53, Smylers wrote: > Dr Bean writes: > > I've gotten comfortable with Test::More conventions, but it's > > difficult in my editor to really quickly create lots of tests. > > Which editor is that? > > > is($o->index('You'), 1, 'objects index 1'); > > isnt($o->index

Re: Activestate and Scalar-List-Utils

2006-03-15 Thread Tels
Moin, On Tuesday 14 March 2006 23:24, Jan Dubois wrote: > On Tue, 14 Mar 2006, David Golden wrote: > > Steve Peters wrote: > > > The problem was that newer Scalar-List-Utils uses an internal Perl > > > function that Windows does not see as an exported function. This > > > was changed with Perl 5.8

Re: getting round Test::More test formatting trickiness

2006-03-15 Thread Tels
moin, On Wednesday 15 March 2006 10:50, A. Pagaltzis wrote: > * Smylers <[EMAIL PROTECTED]> [2006-03-15 09:05]: > >If your editor happens to be Vim then be aware that Ctrl+A adds > >1 to the number currently under the cursor, or the next number > >on the current line if the cursor isn't on a numbe

Best Practice for testing compilation of scripts

2006-03-15 Thread Jeffrey Thalhammer
Putting aside the argument that most logic should be in libraries and not scripts, what is the best practice for writing test cases to verify that your Perl scripts compile? My quick and dirty solution is something like: use Test::More tests => 1; chomp (my $output = `perl -c $script 2>&1`); i

Re: Best Practice for testing compilation of scripts

2006-03-15 Thread chromatic
On Wednesday 15 March 2006 12:25, Jeffrey Thalhammer wrote: > I'm sure I could clean this up by opening a pipe > instead of using backticks and output redirection. > But even that doesn't smell very good. I've looked > around on CPAN, but I have not yet found a Test:: > module that seems appropri

Re: Best Practice for testing compilation of scripts

2006-03-15 Thread Geoffrey Young
chromatic wrote: > On Wednesday 15 March 2006 12:25, Jeffrey Thalhammer wrote: > > >>I'm sure I could clean this up by opening a pipe >>instead of using backticks and output redirection. >>But even that doesn't smell very good. I've looked >>around on CPAN, but I have not yet found a Test:: >>

Re: Best Practice for testing compilation of scripts

2006-03-15 Thread Tels
Moin, On Wednesday 15 March 2006 21:29, chromatic wrote: > On Wednesday 15 March 2006 12:25, Jeffrey Thalhammer wrote: > > I'm sure I could clean this up by opening a pipe > > instead of using backticks and output redirection. > > But even that doesn't smell very good. I've looked > > around on C

Re: Best Practice for testing compilation of scripts

2006-03-15 Thread Chris Dolan
On Mar 15, 2006, at 2:47 PM, Geoffrey Young wrote: chromatic wrote: On Wednesday 15 March 2006 12:25, Jeffrey Thalhammer wrote: I'm sure I could clean this up by opening a pipe instead of using backticks and output redirection. But even that doesn't smell very good. I've looked around on CPA

[FWD: Re: FAIL threads-1.09 MSWin32-x86-multi-thread 4.0]

2006-03-15 Thread Jerry D. Hedden
> Subject: Re: FAIL threads-1.09 MSWin32-x86-multi-thread 4.0 > From: Max Maischein <[EMAIL PROTECTED]> > Date: Wed, March 15, 2006 4:43 pm > To: "Jerry D. Hedden" <[EMAIL PROTECTED]> > > Jerry D. Hedden wrote: > > Would you mind running this again? I tested this against ActivePerl > > 5.8.0/1/2/3

Re: Best Practice for testing compilation of scripts

2006-03-15 Thread Adam Kennedy
http://search.cpan.org/src/ADAMK/ThreatNet-Bot-AmmoBot-0.10/t/01_compile.t That function should probably be changed to use FindBin instead of updir() calls. Actually, by modern standards I'd consider that a pretty half-assed. Mostly for the fact it's a highly unix usage. If it was doing it

Re: getting round Test::More test formatting trickiness

2006-03-15 Thread A. Pagaltzis
* Tels <[EMAIL PROTECTED]> [2006-03-15 17:45]: >Wow. Thanx! (And I have used vim for years...) I hope the fabled “Vim for vimmers” tutorial gets written one day. (It was supposed to be a guide to vim’s advanced features for people who have been using vim for years but have stuck with the basics.)

Re: Best Practice for testing compilation of scripts

2006-03-15 Thread Geoffrey Young
>>> I've long intended to take t/test.pl from the Perl core distribution >>> and wrap >>> up at least its runperl() in a Test:: module. Perhaps that would >>> work for >>> you? >> >> >> compile_ok() ? >> >> --Geoff >> > > It is unclear from Geoff's message above whether he is asserting that >

Re: Best Practice for testing compilation of scripts

2006-03-15 Thread chromatic
On Wednesday 15 March 2006 18:43, Geoffrey Young wrote: > I was suggesting the functionality be added to Test::More as compile_ok(), > rather than runperl() in some separate CPAN module, as it seems to closely > parallel use_ok() for modules and would be rather useful on a larger scale. That woul

Re: Best Practice for testing compilation of scripts

2006-03-15 Thread Tyler MacDonald
Geoffrey Young <[EMAIL PROTECTED]> wrote: > I was suggesting the functionality be added to Test::More as compile_ok(), > rather than runperl() in some separate CPAN module, as it seems to closely > parallel use_ok() for modules and would be rather useful on a larger scale. I agree, a well