Re: (pugs) Managing pleac

Autrijus, let me convert a few recipes first, to earn it ;-) I guess the only thing I'd really like to see is a lot of random community improvements around commits to the recipes, for one. I know that I've got a long way to "getting" the best practices for Perl 6. I guess my sense of versioned sou

CVS going away

I've disabled all CVS write permissions as part of the transition. (Yes, this means wheels are turning.)

Re: (pugs) Managing pleac

On Sat, Apr 09, 2005 at 10:17:12PM -0600, Luke Palmer wrote: > gcomnz writes: > > I'd really like to contribute, but I'm wondering if for the first > > phase a wiki would help the community pull together the best practice > > for each recipe? > > Yes, yes, yes. I am a strong believer in wiki, es

Re: (pugs) Managing pleac

gcomnz writes: > I'd really like to contribute, but I'm wondering if for the first > phase a wiki would help the community pull together the best practice > for each recipe? Yes, yes, yes. I am a strong believer in wiki, especially when most changes are small refactors rather than large rethinki

Re: Question about $pair.kv

Stevan Little writes: > One tests shows $pair.kv returning an array with two elements (the key > and value of the pair). (This is also how Pugs currently implements > this.) > > Another test shows $pair.kv returning an array with one element which > is an array-ref/list which itself has 2 eleme

Re: (pugs) Managing pleac

I'd really like to contribute, but I'm wondering if for the first phase a wiki would help the community pull together the best practice for each recipe? I'm thinking mediawiki style, where there's a discussion page attached to each wiki page. Would it help the conversation progress quickly (and gro

Re: Question about $pair.kv

--- Stevan Little <[EMAIL PROTECTED]> wrote: > Autrijus asked me to look into the correct behavior for $pair.kv > One tests shows $pair.kv returning an array with two elements (the > key > and value of the pair). (This is also how Pugs currently implements > this.) > > Another test shows $pair.

Re: pugs on win32: perl5 and perl6 include paths mix

On Sat, Apr 09, 2005 at 10:11:17PM +0200, Dmitry Karasik wrote: > $ C:\usr\bin\perl.exe -Iinc -MExtUtils::Command -e cp script/pugscc > C:\home\src\pugs\blib\script\pugscc > $ pl2bat.bat C:\home\src\pugs\blib\script\pugscc > $ C:\usr\bin\perl.exe -Iinc util\src_to_blib.pl > Perl v6.0.0 required--t

(pugs) Managing pleac

http://groups-beta.google.com/group/perl.perl6.language/browse_frm/thread/b29d689814d0a50e/bd6ed3ba5ee17ffb#bd6ed3ba5ee17ffb Following up on Tim Bunce's April 1st suggestion that we implement PLEAC (http://pleac.sourceforge.net/), I've gotten a few things started in examples/pleac, but I think it'

(pugs) Managing pleac

http://groups-beta.google.com/group/perl.perl6.language/browse_frm/thread/b29d689814d0a50e/bd6ed3ba5ee17ffb#bd6ed3ba5ee17ffb Following up on Tim Bunce's April 1st suggestion that we implement PLEAC (http://pleac.sourceforge.net/), I've gotten a few things started in examples/pleac, but I think it'

Question about $pair.kv

Hello all, Autrijus asked me to look into the correct behavior for $pair.kv yesterday, and I have been doing some spring cleaning of the Pugs test suite, and found we actually have two conflicting tests for it. So I am asking here to see what the official word is so that I can correct our tests

pugs on win32: perl5 and perl6 include paths mix

Hi all, I'm trying pugs on win32, and there seems to be a clash between perl5 and perl6 include paths during the make process, because the error looks like this: $$ nmake $ C:\usr\bin\perl.exe -Iinc -MExtUtils::Command -e cp script/pugscc C:\home\src\pugs\blib\script\pugscc $ pl2bat.bat C:\home\

Re: best practices for returning a "technical failure" page to a web browser?

On Tue, Apr 05, 2005 at 01:13:53PM +, Mark Stosberg wrote: > As part of building web applications, I sometimes return a "technical > failure" page to the web browser when something unexpected happens that > seems like the software's fault. > > I'm wondering if it's the right thing to do to re

ITypes (was: [Pugs] Some slice oddities)

On Sat, Apr 09, 2005 at 08:48:59PM +1000, Andrew Savige wrote: > I noticed some changes in Pugs behaviour when trying to update the > golf tests (I will update them in svn within 24 hours, I hope). I'm > not certain they are bugs, hence this email. They are. I concluded this week that Pugs's curr

Re: [perl #34894] [PATCH] remove warnings from classes/*.pmc

Jerry Gay <[EMAIL PROTECTED]> wrote: > this patch removes uninitialized variable warnings from the following: Thanks, applied + leftovers from src/string.c leo

[Pugs] Some slice oddities

I noticed some changes in Pugs behaviour when trying to update the golf tests (I will update them in svn within 24 hours, I hope). I'm not certain they are bugs, hence this email. This looks like a bug to me (it used to work): # cat head5.p6 my @x = ( 'a1', 'a2', 'a3' ); say(@x[0..2]); # pugs he

Re: Probing requirements

From: "Randy W. Sims" <[EMAIL PROTECTED]> > I didn't like the Probe name too much at first, but it's kinda grown on > me; seems very perlish. I've come to think of Config::* as a place for > static configuration information such as the compiler used to compiler > perl, $Config{cc}. Probe to me im

Re: Probing requirements (was: Re: Some ideas)

In article <[EMAIL PROTECTED]>, Randy W. Sims <[EMAIL PROTECTED]> wrote: > Probe::OS - Gather info on the operating system > Probe::Libs > Probe::Progs > Probe::FileSys - maybe incorporate ideas Schwern posted on p5p recently, Perhaps we can put this under a namespace like Config:: ? I imagi

Re: [perl #34893] [PATCH] remove warnings from dynclasses/tcl*.pmc

Jerry Gay <[EMAIL PROTECTED]> wrote: > this patch removes warnings of unreferenced labels and local variables from > dynclasses/tcl*.pmc Thanks, applied. leo

Re: [perl #34891] [PATCH] remove 'unreferenced local variable' warnings from src/*.c files

Jerry Gay <[EMAIL PROTECTED]> wrote: > i'm in the process of removing warnings from parrot, and i thought i'd split > the patches up into manageable chunks. Splitting bigger patches is good, it simplifies review. > ... this patch removes 'unreferenced > local variable' warnings from all src/*.c

Re: Dynamic Perl, Part 1 [IMCC]

William Coleda <[EMAIL PROTECTED]> wrote: > Attached, find the first trivial chunk, which removes as much Perl* > from IMCC internals and tests as possible without writing actually > writing any new PMC code. Applied the trivial part, i.e. all but the change to PMCArray. > PerlArray is going to

Re: [PATCH] update pcre example + libraries + tests

jerry gay wrote: wouldn't you know it... i upload the wrong patch. here's the correct one, with all tests passing on win32. On Apr 7, 2005 9:00 AM, *jerry gay* <[EMAIL PROTECTED] > wrote: i've attached a patch to update the pcre example, libraries, and added so