Categories
Posts in this category
- A shiny perl6.org site
- Creating an entry point for newcomers
- Sprixel, a 6 compiler powered by JavaScript
- Another perl6.org iteration
- Blackjack and Perl 6
- Why I commit Crud to the Perl 6 Test Suite
- Report from the Perl 6 Hackathon in Copenhagen
- Custom operators in Rakudo
- Defined Behaviour with Undefined Values
- Dissecting the "Starry obfu"
- Perl 6: Failing Softly with Unthrown Exceptions
- The first Perl 6 module on CPAN
- Google Summer of Code Mentor Recap
- Building a Huffman Tree With Rakudo
- Immutable Sigils and Context
- Is Perl 6 really Perl?
- Perl 6: Lost in Wonderland
- Lots of momentum in the Perl 6 community
- Musing and the future of feather and the Pugs repository
- Musings on Rakudo's spectest chart
- My first executable from Perl 6
- Trying to implement new operators - failed
- Let's build an object
- Perl 6 is optimized for fun
- How to get a parse tree for a Perl 6 Program
- Perl 6 in 2009
- Perl 6 ticket life cycle
- The Perl 6 Advent Calendar
- How to Plot a Segment of a Circle with SVG
- Publicity for Perl 6
- Rakudo architectural overview
- Rakudo Rocks
- Rakudo "star" announced
- Rakudo's rough edges
- Rats and other pets
- Releasing Rakudo made easy
- Set Phasers to Stun!
- Starry Perl 6 obfu
- Recent Perl 6 Developments August 2008
- Strings and Buffers
- Subroutines vs. Methods - Differences and Commonalities
- A SVG plotting adventure
- A Syntax Highlighter for Perl 6
- Test Suite Reorganization: How to move tests
- The Happiness of Design Convergence
- Perl 6 Tidings from September and October 2008
- Perl 6 Tidings for November 2008
- Perl 6 Tidings from December 2008
- Perl 6 Tidings from January 2009
- Perl 6 Tidings from February 2009
- Perl 6 Tidings from March 2009
- Perl 6 Tidings from April 2009
- Perl 6 Tidings from May 2009
- Perl 6 Tidings from May 2009 (second iteration)
- Perl 6 Tidings from June 2009
- Perl 6 Tidings from August 2009
- Perl 6 Tidings from October 2009
- Timeline for a syntax change in Perl 6
- Visualizing match trees
- We write a Perl 6 book for you
- When we reach 100% we did something wrong
- Where Rakudo Lives Now
- Why was the Perl 6 Advent Calendar such a Success?
- What you can write in Perl 6 today
- Why you don't need the Y combinator in Perl 6
Sun, 04 Oct 2009
Sprixel, a 6 compiler powered by JavaScript
Permanent link
Today I want to announce sprixel, a new Perl 6 compiler in its early stage of development, written in JavaScript and using the standard Perl 6 grammar STD.pm.
Sprixel (an anagram of perlsix) development was initiated by Matthew Wilson, aka diakopter. It traverses the Abstract Syntax Tree as produced by STD.pm, transforms it into an intermediate JavaScript data structure similar to JSON (but with some enhancements to handle cyclic structures), and has a small, continuation based runloop that executes the JavaScript. Currently the only backend is the V8 compiler and virtual machine - but if/when the STD grammar is implemented, you'll be able to run Perl 6 in your browser.
Currently sprixel supports scalar and list variables, numbers (including bigint), strings, string interpolation, basic control flow, closures, named sub declaration (with parameters), and map.
Sprixel development is optimized for fun, and already picked up some contributors (notably, mberends implemented many infix operators, a makefile, and a test harness). The source code can be found in the pugs repository (but is completely independent of the pugs compiler project). The main communication medium so far has been the #perl6 IRC channel on irc.freenode.net.
Motivation
Why yet another Perl 6 implementation? you might ask. A few reasons actually:
- Sprixel exercises STD.pm, which so far is mostly tested only for parse successes or failures. Relying on the underlying AST structure in a real compiler helps to reveal tricky bugs and unnecessarily difficult interfaces.
- Most existing Perl 6 compilers either implement only a minimal subset of Perl 6, or rely heavily on a rather large stack of underlying software, thus making substantial contributions non-trivial.
- Implementing a compiler helps one to understand the language better.