Re: [Summary] Help

2004-06-19 Thread Piers Cawley
Piers Cawley <[EMAIL PROTECTED]> writes: [...] > Thanks in advance. And thanks to Sebastian Riedel, Brent Royal-Gordon, Robert Spier and the aforementioned Jeffrey Dik I have filled in my lacunae and I'm ready to get my summary on when Monday rolls around.

Re: [Summary] Help

2004-06-19 Thread Piers Cawley
Piers Cawley <[EMAIL PROTECTED]> writes: > For various annoying reasons involving a pernickety external drive and > a service centre that, after more than a week *still* hasn't taken a > look at my main machine, I find myself missing a tranche of messages to > perl6-internals and perl6-language. I

Re: testing for unsuccessful require - mocking require ?

2004-06-19 Thread stevan little
Gabor, Maybe you could try using the [EMAIL PROTECTED] trick to do what you want? You could unshift a sub ref onto @INC right before the test which would mock the loading failure for Foo and only Foo. Then as soon as your test is finished, you can shift it back off again. unshift @INC => sub {

[Summary] Help

2004-06-19 Thread Piers Cawley
For various annoying reasons involving a pernickety external drive and a service centre that, after more than a week *still* hasn't taken a look at my main machine, I find myself missing a tranche of messages to perl6-internals and perl6-language. If some kind soul were to send me mbox files contai

Re: My Phalanx lightning talk

2004-06-19 Thread Mark Fowler
On Thu, 10 Jun 2004, Andy Lester wrote: > I'm thinking that maybe instead of people picking a module to do, and > then working on it, which has so far not worked at all, that we should > hold up a module (or a handful of them) and say "OK, this is what we're > working on". It certainly seemed to

Re: testing for unsuccessful require - mocking require ?

2004-06-19 Thread Kate L Pugh
On Sat 19 Jun 2004, Gabor Szabo <[EMAIL PROTECTED]> wrote: > I would like to test a module for unsuccessful "require" while the > required module is installed. That is I'd like ot test how my code would > work if Foo.pm was not present. Max Maischein wrote Test::Without::Module to do this. (This

Re: testing for unsuccessful require - mocking require ?

2004-06-19 Thread Paul Johnson
On Sat, Jun 19, 2004 at 09:11:43PM -0200, Gabor Szabo wrote: > > I would like to test a module for unsuccessful "require" while the > required module is installed. That is I'd like ot test how my code would > work if Foo.pm was not present. > > In the middle of a module I have code such as > > e

Re: testing for unsuccessful require - mocking require ?

2004-06-19 Thread Fergal Daly
Below is Hide.pm, you can use it like this use Hide qw( Foo ); require Bar; # will be fine require Foo; # will fail I just wrote it now. It seems to work (even if @INC already contains subrefs, arrayrefs or objects). You can even use it twice and everything should just work. It seems to have a p

Re: testing for unsuccessful require - mocking require ?

2004-06-19 Thread Andrew Pimlott
On Sat, Jun 19, 2004 at 09:11:43PM -0200, Gabor Szabo wrote: > > I would like to test a module for unsuccessful "require" while the > required module is installed. That is I'd like ot test how my code would > work if Foo.pm was not present. > > In the middle of a module I have code such as > > e

Re: how to run test.pl before the t/*.t tests ?

2004-06-19 Thread _brian_d_foy
In article <[EMAIL PROTECTED]>, Gabor Szabo <[EMAIL PROTECTED]> wrote: > So first I thought to try to run test.pl before the t/-tests. Hence the > subject. How to do this is still interesting, though maybe not necessary: You used to be able to set the order of tests through MakeMaker, then that f

testing for unsuccessful require - mocking require ?

2004-06-19 Thread Gabor Szabo
I would like to test a module for unsuccessful "require" while the required module is installed. That is I'd like ot test how my code would work if Foo.pm was not present. In the middle of a module I have code such as eval { require Foo; }; if ($@) { foo(); } else { my_own_foo(); } I a

Re: Slices and iterators

2004-06-19 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > Px = Py[Pz] > won't be, and we'll need to note whether Pz should be taken as an > int, string, or PMC. (PMC for the fancier keying of hashes) > ... A simple :i, :s, :p [...] suffix Do we really need that? The aggregate is responsible to do the righ

Re: [perl #30344] [PATCH] nmake clean fixes

2004-06-19 Thread Leopold Toetsch
Dennis Rieks <[EMAIL PROTECTED]> wrote: > some changes to run "nmake clean" on windows with nmake / vc6. Thanks, applied. leo

Re: Big nums

2004-06-19 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > Time for these as well. There's a partial implementation of them in > types/bignum.c. I think it's time to move that to src/ (and the > header file to .h) and get it integrated into parrot. Anyone working on that? Who volunteers? leo

Re: [perl #30349] [PATCH] Fix Win32 building part 1

2004-06-19 Thread Leopold Toetsch
Jonathan Worthington <[EMAIL PROTECTED]> wrote: > The attached one-line patch sorts out something that stopped ICU build > working on Win32 with Visual Studio 6.0. Thanks, applied. leo

Re: [perl #30320] [PATCH] Minor build patches for languages/m4

2004-06-19 Thread Leopold Toetsch
Andrew Dougherty <[EMAIL PROTECTED]> wrote: > On Thu, 17 Jun 2004, Leopold Toetsch via RT wrote: >> Andy Dougherty <[EMAIL PROTECTED]> wrote: >> >> > This patch assumes my previous Configure.pl patch for c++ detection has >> > been included. >> >> Which ticket number? > Oops. Sorry to be vague -

Re: one shootout result

2004-06-19 Thread Leopold Toetsch
Sean O'Rourke <[EMAIL PROTECTED]> wrote: > Leopold Toetsch <[EMAIL PROTECTED]> writes: >> get_pmc_const P0, "_fib" >> invokecc > This isn't really kosher -- since "fib" might have been redefined in > the current lexical environment, we have to (at least conceptually) > find its lexical. Bai

Re: how to run test.pl before the t/*.t tests ?

2004-06-19 Thread darren chamberlain
* Gabor Szabo [2004/06/18 23:34]: > I am trying to add a bunch of tests in t/ using Test::More but in > order to make sure we don't lose any previous test we would like to > keep the test.pl file as it is. Is porting the tests in test.pl to *.t files not an option? (darren) -- Never doubt that