Justin Meza
unread,Dec 28, 2010, 1:52:17 AM12/28/10Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to lci-devel
I forget the exact date (definitely around the 1st of the year) that I
had a working interpreter but, hey, now is as good of a time as any to
celebrate lci's 1st birthday! Looking back, a lot has actually been
accomplished in the interpreter over the past year, with nearly all of
the 1.3 additions implemented. Speaking of implementations, time for
an update.
I am currently testing an implementation of BUKKITs. To help spot
logical bugs, I'm writing a BF interpreter in LOLCODE. If things work
well, I will be adding inheritance and the rest of the 1.3 spec and
then its on to... wait, what comes next? I guess that's a topic for
another time.
Because the BF interpreter is rather long-ish and LOLCODE is not the
most, shall we say, _legible_ programming language, I've made a Vim
syntax highlighting file (which I'll release eventually, but I'm still
adding to right now).
I've started using a lint program, splint, to identify potential bugs
or just bad programming practices in the code. With all options on it
can be pretty noisy, so I've tamed it down in the Makefile to just a
subset of the things it can check for which I think make sense. (Most
of the turned-off options are warnings about possible memory leaks
which are already checked for by valgrind and handled properly.)
That's all for now, BUKKITs are definitely going to take some more
work to get just right, but they're getting there. Stay tuned for
updates.