I've finally got around to adding perlundef.pmc, which means that the
classes/Makefile has changed; this means you'll all - and tinderbox people
especially - have to rerun Configure. I suppose someone should add tests
for perlundef.pmc, but I hate writing tests. :) (Especially if I think
they might fail. ;)
Since 0.0.3 is exceptionally imminent, can I have a roll-call of systems
which are working and not working?
The other change I made today was to make the assembler understand
new P0, PerlInt
new P1, PerlString
and so on. (I've also updated the tests to reflect this.)
I'm marginally happier about documentation now that I've seen the
automatically generated stuff, but I want four more documents to go into
Parrot before 0.0.3: basic introduction and roadmap to documentation, the
(rest of the) vtables docs, some documentation on the bytecode format, and
a basic guide to programming Parrot, getting stuff compiled, etc.
The last one (parrotintro.pod) can be cobbled together from my perl.com
article and some stuff from parrotcode.org - I'll do that tonight.
If anyone wants to write the bytecode documentation and the
introduction/roadmap, I'd be thrilled.
--
In a sense Christianity is like Jazz - if you need to ask the questions
you won't understand the answers.
- Bob Billing
