From mark at purdue.edu  Thu Nov  8 09:57:52 2007
From: mark at purdue.edu (Mark Senn)
Date: Thu, 08 Nov 2007 12:57:52 -0500
Subject: [Purdue-pm] Perl Mongers LinkedIn group
Message-ID: <10756.1194544672@pier.ecn.purdue.edu>

(To the two people bcc'd: you can sign up for the Pudue Perl Mongers
mailing list at
    purdue-pm at pm.org
if you'd like.)

A forwarded message that may be of interest:
    To: pm_groups at pm.org
    From: Jos? Alves de Castro <jose at pm.org>
    Date: Thu, 8 Nov 2007 17:05:26 +0000
    Subject: [pm_groups] Perl mongers around the world, unite!
    Sender: pm_groups-bounces+mark=purdue.edu at pm.org
    
    At least on LinkedIn, for now.
    
    We just created a LinkedIn group for Perl Mongers.
    
    Enjoy and join the group at
        http://www.linkedin.com/e/gis/40830/4971AC40763D
    
    Cheers!
    
    jac
    
    PS: Please do pass the message on to your pm groups.
    
    --
    Jose Castro
    TPF Community Relations Leader

Mark Senn, restarted the Purdue Perl Mongers in 2006 after
           it was inactive several years

From westerman at purdue.edu  Tue Nov 13 06:12:27 2007
From: westerman at purdue.edu (Rick Westerman)
Date: Tue, 13 Nov 2007 09:12:27 -0500
Subject: [Purdue-pm] Reminder: Technical meeting tonight, Nov. 13th
Message-ID: <4739B0CB.8000908@purdue.edu>

   Reminder that the Perl Mongers technical meeting is tonight from 5:30 
to 7:00 in ME 119.  At the moment we have 3 speakers -- myself talking 
about Perl test beds and data driven programming, a couple of short 
topics from Mark, and a talk from Doug.


-- 
Rick Westerman westerman at purdue.edu Bioinformatics specialist at the 
Genomics Facility. Phone: (765) 494-0505 FAX: (765) 496-7255 Department 
of Horticulture and Landscape Architecture 625 Agriculture Mall Drive 
West Lafayette, IN 47907-2010 Physically located in room S049, WSLR 
building

From mark at purdue.edu  Mon Nov 26 08:26:15 2007
From: mark at purdue.edu (Mark Senn)
Date: Mon, 26 Nov 2007 11:26:15 -0500
Subject: [Purdue-pm] Current roadmap for Perl 6 on Parrot
Message-ID: <7290.1196094375@pier.ecn.purdue.edu>

Purdue Perl Mongers mailing list,

Thought you might be interested in the following message.

Mark

Date: Sat, 24 Nov 2007 12:33:37 -0600
From: "Patrick R. Michaud" <pmichaud at pobox.com>
To: perl6-compiler at perl.org, parrot-porters at perl.org
Subject: Current roadmap for Perl 6 on Parrot

I've just written up a brief "road map" with the current status
and development plans for the Perl 6 on Parrot compiler, and
thought I'd share it here as well.  It's also available as
languages/perl6/ROADMAP in the Parrot repository, for people
who want to look at it there.

Before going too far, I should point out that there are several
Perl 6 language translators in progress -- at least two of these 
include Pugs and KindaPerl6.  These are available from 
http://www.pugscode.org/ , and I highly recommend looking at
the work they are doing.  In particular, if writing Perl 6
programs is your interest (as opposed to developing a compiler), 
then Pugs currently supports the widest set of Perl 6 language 
features.


Building the Perl 6 on Parrot compiler
--------------------------------------

The compiler and toolchain that I've been focusing on developing
is for the Parrot virtual machine ( http://www.parrotcode.org/ ).
The Perl 6 Compiler for Parrot is called "perl6", and it currently
lives in the languages/perl6/ directory of the Parrot repository.

To build the perl6 compiler, first get a working copy of Parrot,
then change to the languages/perl6/ subdirectory and type "make".
This will build the compiler into a file called "perl6.pbc".
The ".pbc" stands for "Parrot bytecode", and represents an
an executable Parrot module.

To run a program with perl6, one then issues a command like

    $ parrot perl6.pbc hello.pl

Parrot does not yet support a #! syntax that allows us to run
Perl 6 scripts directly from the command line, but that will
undoubtedly be coming soon.

If the perl6 compiler is invoked without a script argument
(i.e., "parrot perl6.pbc"), it enters a small interactive 
mode that allows Perl 6 statements to be executed from the 
command line.

After the compiler is built, one can run "make test" to run
the local test suite, or "make spectest" to download and run
selected tests from the Pugs repository.

I will note here that we've all collectively decided that the
Pugs repository will be the home of the "official Perl 6 test
suite" for the forseeable future.  Thus, it's the source of
tests that all of the development efforts should target.
A lot of effort over the next few months will be spent
in re-organizing the test suite and ensuring that it accurately
reflects the current Perl 6 specification as given by the 
synopses documents ( http://dev.perl.org/perl6/doc/synopsis.html ).


Structure of the compiler as of 2007-11-01
------------------------------------------

Before describing where we're going, it may be useful to briefly
outline where we've been.  As of early November 2007, the 
perl6 compiler is divided up into four major components:

1.  the parsing grammar (src/parser/Grammar.pg)
2.  some parsing support subroutines (src/parser/*.pir)
3.  the AST transformation (src/PAST/Grammar.tg)
4.  runtime support (src/builtins/, src/classes/, src/pmc/)   

The parsing grammar is written using Perl 6 regular expressions
(Synopsis 5) -- the version of regular expressions that were in 
effect at the beginning of the year.  More on this in a bit.  
The Parser Grammar Engine (PGE) is used to compile the grammar 
into a working parser.  The parsing support routines are used 
to parse constructs (e.g., quoted literals) that are more easily 
parsed procedurally than with regular expressions.

The AST transformation uses another tool called the Tree
Grammar Engine (TGE) to convert a parse tree into an
abstract syntax tree representation known as PAST-pm.  The
PAST-pm toolchain is then able to perform the remainder of
the code generation and execute the program.

The runtime support consists of some basic types and operators,
which are currently written in a mix of PIR and C.  Extensions
are expected to be bootstrapped using Perl 6.


Where things are headed next
----------------------------

While the design and implementation of the perl6 compiler has
remained fairly static throughout 2007, a number of other things
have been occurring that will spark a substantial redesign.

First, as of Parrot 0.5.0 we now have a shiny new object model 
that eliminates many of the obstacles that had been impeding 
work on the compiler.  

Another significant change has been the development of a
standard grammar for Perl 6, known as STD.pm [1].  Larry started
the STD.pm grammar earlier this year based on the grammars written 
for Pugs and perl6, and partially as a result of this grammar 
there's been some substantial redesign and improvement to 
Synopsis 5 (Regexes).  

So, one of the things we will be doing soon is to redesign the
perl6 compiler using a grammar that is much closer to STD.pm .
We aren't quite ready to use STD.pm directly, because it relies
somewhat on having a working Perl 6 implementation, as well
as some new constructs that aren't implemented by Parrot's
regex engine.  It may be a while before all of this is ready,
so we'll use a modified-but-similar-structure grammar for now,
and work towards convergence with STD.pm .

A big improvement in the regex syntax and STD.pm grammar
is that they provide a useful syntax for embedding actions
directly into the grammar (using the sequence {*} ).  
As a result, the AST can be generated as part of the parsing
phase, instead of requiring a separate phase.

Furthermore, the methods for generating the AST can be written in
in "NQP" instead of Parrot assembly.  NQP is a lightweight form
of Perl 6 designed especially for compiling simple programs in
Parrot [2].  As a result, most of the source code for the perl6 
compiler will end up looking a lot like Perl 6, which may make
it easier for others to hack on.  

So, here's the current plan for the next couple of weeks:

* NQP will get one or two more language constructs added to it,
  to support generating simple class and method definitions.

* The perl6 grammar will then be redesigned to more closely
  mimick STD.pm .  Actually, we'll use NQP's current grammar
  as a starting point, since it's been designed based on STD.pm .
  We'll want to work on this to get perl6 at least back to the
  level of passing tests that it has now.

* In the process we'll also be doing some redesign of the runtime
  environment and built-in classes, to take advantage of Parrot's
  new object model.

As we get perl6 re-oriented in the new constellation of tools,
we can then continue to address language features, builtin classes
and methods, and otherwise add features to flesh out the
compiler implementation.  Much of this will be driven by
the test suite -- i.e., we'll identify tests that we want to
have passing, and add the code to make that happen.

At the same time, we'll also be conducting reviews of what's
currently in the test suite to make sure it continues to honor
the specs in the Synopses.  Some of the tests have never been
fully reviewed, and the Synopses have subtly changed over time,
so this is a good chance to make sure they're correct.


How others can start hacking and contributing
---------------------------------------------

If you're interested in hacking on the compiler, my suggestion 
is to become somewhat familiar with the compiler tools already 
available in Parrot.  The mostly likely place to start is to look
at the implementation of NQP and see how it has been
put together.  The grammar for NQP is written in Perl 6,
and although the AST transformations are currently written
in PIR, the source code for the transformations also provides
the Perl 6 equivalent.  (Eventually NQP may be used to 
bootstrap itself... but we're not there yet, and I'm more
focused on getting perl6 running.)

Patches and bug reports can be submitted to perl6-bug at perl.org.  
Please use the moniker [PATCH], [BUG], or [TODO] (including the 
brackets) at the start of the subject so that RT can appropriately
tag the item.

Lastly, feel free to ask questions on the mailing lists and
on IRC.  Most of the people working on Parrot tend to hang
out on #parrot on irc.perl.org, and all are welcome to
ask questions there.  As questions arise we should also
make a record of them so that others will be able to more
easily follow.

Thanks for reading!

Pm

References:

1.  STD.pm:  http://svn.pugscode.org/pugs/src/perl6/STD.pm
2.  NQP:     http://svn.perl.org/parrot/trunk/languages/nqp/