[Fwd: Re: Moving the p5 standard library to p6]

2005-03-26 Thread chromatic
Forwarded... On Sat, 2005-03-26 at 12:05 +1100, Andrew Savige wrote: Please note that I am not an expert on any of this, I was just wondering whether we are going to clean up the old p5 library interfaces as part of the move to p6. Or must we support the old p5 library interfaces for

Re: [Fwd: Re: Moving the p5 standard library to p6]

2005-03-26 Thread Juerd
chromatic skribis 2005-03-26 2:13 (-0800): No. Please, no. :) As I see it, Perl 6 has a chance to start over with a very small set of core libraries -- perhaps embarrassingly small -- so as not to entomb our current, potentially-blepharitic guesses at good Perl 6 design principles for the

Re: [Fwd: Re: Moving the p5 standard library to p6]

2005-03-26 Thread Larry Wall
On Sat, Mar 26, 2005 at 11:31:07AM +0100, Juerd wrote: : Perhaps good administration would be to introduce a generic Deprecated:: : namespace. Module authors can move their own old modules there if they : want, and there can be Deprecated::P5 for stuff like dbmopen, :

Moving the p5 standard library to p6

2005-03-25 Thread Andrew Savige
I noticed the Pugs folks have started porting File::Spec and other modules to Pugs, which leads me to ask this question. I've also taken a look at Rod Adams S29. There a quite a few p5 standard libraries with crusty old user interfaces that many folks dislike. Two that people often seem to

Re: Moving the p5 standard library to p6

2005-03-25 Thread Larry Wall
On Sat, Mar 26, 2005 at 12:05:06PM +1100, Andrew Savige wrote: : I noticed the Pugs folks have started porting File::Spec and : other modules to Pugs, which leads me to ask this question. : I've also taken a look at Rod Adams S29. : : There a quite a few p5 standard libraries with crusty old user