Parrot is a virtual machine designed to efficiently compile and execute bytecode for dynamic languages. Parrot currently hosts a variety of language implementations in various stages of completion, including Tcl, Javascript, Ruby, Lua, Scheme, PHP, Python, Perl 6, APL, and a .NET bytecode translator. Parrot is not about parrots, though we are rather fond of them for obvious reasons.
Submitted by dukeleto on Wed, 10/19/2011 - 02:08
On behalf of the Parrot team, I'm proud to announce Parrot 3.9.0 "Archaeopteryx".
Parrot (http://parrot.org/) is a virtual machine aimed at running all dynamic languages.
Parrot 3.9.0 is available on Parrot's FTP site
(ftp://ftp.parrot.org/pub/parrot/releases/supported/3.9.0/), or by following the
download instructions at http://parrot.org/download. For those who would like
to develop on Parrot, or help develop Parrot itself, we recommend using Git to
retrieve the source code to get the latest and best Parrot code.
Submitted by benabik on Wed, 10/05/2011 - 21:14
TL;DR: https://github.com/parrot/PACT
So after my last blog post, I started a gist to keep track of "how would I write PCT". I called it PACT, the Parrot Alternate Compiler Toolkit. I suppose I could have called it PCT2, but I really don't want to try to claim it will 100% replace PCT. PCT's very valuable to the people using it right now, but there's no small desire to add to it and I'd like to help it be better. Parrot's main audience, to my mind, is prospective compiler writers and the easier we can make their lives the better.
Submitted by soh_cah_toa on Wed, 09/21/2011 - 03:35
On behalf of the Parrot team, I'm proud to announce Parrot 3.8.0, also known as "Magrathea". Parrot (http://parrot.org/) is a virtual machine aimed at running all dynamic languages.
Parrot 3.8.0 is available on Parrot's FTP site (ftp://ftp.parrot.org/pub/parrot/releases/devel/3.8.0/), or by following the download instructions at http://parrot.org/download. For those who would like to develop on Parrot, or help develop Parrot itself, we recommend using Git to retrieve the source code to get the latest and best Parrot code.
Submitted by tcurtis on Wed, 08/24/2011 - 23:19
The hard "pencils down" date was Monday, so now seems like a good time for a blog post summarizing what I ended up completing.
I have DPDA generation and parsing working for LR(0) and SLR(1) grammars. I have the beginnings of a grammar specification DSL (a grammar, but no actions or tokenizer yet; it's in the dsl branch). I do not have support for LALR(k) grammars or general LR(k) grammars. I have not implemented generating code to parse grammars (as opposed to interpreting the DPDA in order to parse them).
Submitted by benabik on Mon, 08/22/2011 - 05:26
I've spent the last few days cleaning up my branch: adding documentation, checking that it passes the code standard tests, and trying compiling Rakudo nom. Don't get too excited, we can't compile nom directly to bytecode. Heck, it can't compile squaak directly yet. But I wanted to make sure that all my tinkering hasn't broken the original PIR generation path.
Submitted by soh_cah_toa on Sun, 08/21/2011 - 03:32
Actually, I suppose the flight has really just begun. It's true that GSoC is nearly at its end but, ironically enough, it doesn't really feel like the end but more of a new beginning. A new debug data format is in the works and it has so much potential!
Submitted by benabik on Sat, 08/20/2011 - 18:48
While I didn't implement everything I thought I would, there is now a basic framework for bytecode generation in the nqp_pct branch. I'm uncertain if it should be merged... While the bytecode generation doesn't fully work, it doesn't interfere with the existing usage of PCT and does have the nice feature that PAST::Compiler is now written in NQP for ease of hacking. I'll leave that up to the rest of the community to decide. The rest of this blog post is the contents of docs/pct/bytecode.pod, which I hope will be helpful if anyone want to explore what I've been working on all summer.
Submitted by rohit_nsit08 on Sat, 08/20/2011 - 14:22
With only two days left before the hard dead line and that will the end of my first GSOC . These three months has given me a tremendous insight into the world of open source, scripting languages and off-course compilers.
The good parts
Three months ago, I was a programmer who knew how to programme in javascript and few other languages but nothing about what is going inside the compiler which drives a language but now I know what makes javascript so dynamic and powerful ,I know how code is read, converted into tokens and the formation of Syntax tree.
Submitted by bubaflub on Sat, 08/20/2011 - 03:41
It's been a while since I've posted - real life has been crazy with moving and setting up and finals. That's my fault because I didn't take into account the fact that I would be moving nor my finals being right around the time GSoC would be ending. The good news is that I've moved and setup my place (hooray for having my own office) and my classes are done - I've written the last research paper and taken my last final for my masters.
Submitted by rohit_nsit08 on Thu, 08/18/2011 - 14:37
After missing action from some time, Corella is rising again . Right now Corella is not able to compile itself which was intended to but I'm trying to cover as much as possible and will give my best in this week. Corella's object system ("Corella-System") is ready and working.
Worked on arrays today and now corella is having support for arrays and even multi dimentional arrays as given in the ecmaScript.
e.g.
var arr = []
results in
.HLL "corella"
.include "corella_system.pir"
.sub 'main' :main
 |
|
|
|
