Re: Access to the perl6 parser

2000-08-30 Thread Damian Conway
>>http://www.csse.monash.edu.au/~damian/CPAN/Language-Pythonesque-beta.tar.gz > > How close to a complete Python implementation is it? I can see shipping it > as part of perl 5.8.0 if it's close. 6.0.0, too. (And yes, I'm serious) I'm afraid it isn't Python at all. It's Perl without

Re: Access to the perl6 parser

2000-08-30 Thread Dan Sugalski
At 08:50 AM 8/30/00 +1100, Damian Conway wrote: >> Damian Conway wrote: >> > >> >> Regardless, you can already do this in perl 5, and will > undoubtedly >> >> be able to do it in perl 6, with source filters. (If Damian can >> >> write perl that looks like Latin or

Re: Access to the perl6 parser

2000-08-29 Thread Damian Conway
> Damian Conway wrote: > > > >> Regardless, you can already do this in perl 5, and will undoubtedly > >> be able to do it in perl 6, with source filters. (If Damian can > >> write perl that looks like Latin or Klingon, then python ought to > >> be simple... :)

Re: Access to the perl6 parser

2000-08-29 Thread Christian Soeller
Damian Conway wrote: > >> Regardless, you can already do this in perl 5, and will undoubtedly >> be able to do it in perl 6, with source filters. (If Damian can >> write perl that looks like Latin or Klingon, then python ought to >> be simple... :) > > I have a module (Language::

Re: Access to the perl6 parser

2000-08-29 Thread Jim Edwards
Christian Soeller wrote: > Dan Sugalski wrote: > > > > > Because source filters are: > > > > 1) Relatively new (5.005 IIRC, but I could be mis-remembering) > > 2) A bloody pain in the neck to write > > > > Lots of things could use 'em if they were easier to do. That's one of the > > goals of perl

Re: Access to the perl6 parser

2000-08-29 Thread Damian Conway
> Regardless, you can already do this in perl 5, and will undoubtedly > be able to do it in perl 6, with source filters. (If Damian can > write perl that looks like Latin or Klingon, then python ought to > be simple... :) I have a module (Language::Pythonesque) on that... :-) Damian

Re: Access to the perl6 parser

2000-08-29 Thread Christian Soeller
Dan Sugalski wrote: > > Because source filters are: > > 1) Relatively new (5.005 IIRC, but I could be mis-remembering) > 2) A bloody pain in the neck to write > > Lots of things could use 'em if they were easier to do. That's one of the > goals of perl 6, I think. > Are there any docs in per

Re: Access to the perl6 parser

2000-08-29 Thread Dan Sugalski
At 06:21 PM 8/29/00 +, Jim Edwards wrote: > > > > > > Regardless, you can already do this in perl 5, and will undoubtedly be able > > to do it in perl 6, with source filters. > >So why do we have to do >$ip1=$i+1;# my pdl pet peave >$f->slice("(0),$ip1,$i"); > >instead

Re: Access to the perl6 parser

2000-08-29 Thread Jim Edwards
> > > Regardless, you can already do this in perl 5, and will undoubtedly be able > to do it in perl 6, with source filters. So why do we have to do $ip1=$i+1;# my pdl pet peave $f->slice("(0),$ip1,$i"); instead of $f((0),$i+1,$i); # substitute your favorite syntax

Re: Access to the perl6 parser

2000-08-29 Thread Dan Sugalski
At 06:05 PM 8/29/00 +, Jim Edwards wrote: >IMHO if the perl6 core only allow access to the parser, than a module can >do just about anything including all of those things proposed in RFC 115 - 117. That's sort of on the list of things to allow (I think Damian RFC'd it) but whether it happe

Access to the perl6 parser

2000-08-29 Thread Jim Edwards
IMHO if the perl6 core only allow access to the parser, than a module can do just about anything including all of those things proposed in RFC 115 - 117. Maybe this is an over simplification, but it seems that if the statement: use Python; caused the subsequent source to go through my Python: