Updates

[Justin Meza]

Three things:

1. I'm working on a draft of the LOLCODE language as it will be
implemented after the 1.3 additions are added to lci. You can think
of it as an unofficial LOLCODE language specification version 1.3
(although calling it that might be going a bit too far, but you get
the general idea). The point is that if these features are integrated
into lci, there should be some centralized documentation provided for
how they are used, function, and interact as opposed to a scattered
set of proposals, forum posts, and old specifications.

2. lci will be celebrating it's 1st-ish birthday this upcoming
December and I'd like to have some of my 1.3 changes applied by then.
We'll see how it goes.

3. I've finally realized that Glen was right: a VM approach is the way
to go. One compelling reason is that there is simply no cache
locality present while traversing a parse tree and linked lists of
data objects and I think that that alone could give the interpreter a
nice performance boost. However, I have no experience crafting
virtual machines. There are a couple of books that seem interesting
(http://www.amazon.com/Virtual-Machines-Iain-D-Craig/dp/1852339691/
and http://www.amazon.com/gp/product/1558609105/) but I don't have the
time to read them at the moment so it will probably have to wait.
Interesting stuff, though!

Also, some people have been popping into the IRC channel lately,
almost entirely lurking, but more frequently than in the past. The
one time someone actually spoke I was AFK and they left---go figure.