About half a year ago I posted my idea of a program that explains Perl 6
syntax:
http://www.nntp.perl.org/group/perl.perl6.users/2007/07/msg621.html
Differing from my first post I know think that the best idea is to
really parse a Perl 6 program with a fully fledged parser, and emit some
kind of
On Wed, Jan 30, 2008 at 04:08:04PM +0100, Moritz Lenz wrote:
: About half a year ago I posted my idea of a program that explains Perl 6
: syntax:
:
: http://www.nntp.perl.org/group/perl.perl6.users/2007/07/msg621.html
:
: Differing from my first post I know think that the best idea is to
:
Larry Wall wrote:
On Wed, Jan 30, 2008 at 04:08:04PM +0100, Moritz Lenz wrote:
: About half a year ago I posted my idea of a program that explains Perl 6
: syntax:
:
: http://www.nntp.perl.org/group/perl.perl6.users/2007/07/msg621.html
:
: Differing from my first post I know think that
Moritz Lenz wrote:
I just ran
../../parrot perl6.pbc --target=past t/01-sanity/02-counter.t
and it seems that I'm able to reconstruct the basic structure (I can
identify operators and variables and their position in the source code,
for example), but for example it stores variables this way:
On Jan 30, 2008 10:36 AM, Moritz Lenz [EMAIL PROTECTED] wrote:
Larry Wall wrote:
On Wed, Jan 30, 2008 at 04:08:04PM +0100, Moritz Lenz wrote:
: Do you have any idea how I may circumvent the problem?
:
: I had some thoughts, but none appear to be a good solution:
: * build two trees,
Hi,
I've taken time to look over the patch properly now. I said it would be
good as I patch for the .perl method and that I'd apply it with the name
change, but it actually needs a little more than that. Basically, rather
than just joining the values, you need to loop over them and call .perl
On Wed, Jan 30, 2008 at 07:47:18PM +0100, Moritz Lenz wrote:
: particle++ told me to try --target=parse instead, and that's pretty much
: verbose and all I should ever need ;-)
Hmm, yes, but *only* if that switch merely augments information without
destroying information, and doesn't otherwise
