This release features direct generation of executable binaries,
dramatically improved documentation, and a built-in bread maker! Get
it while it's hot at
<http://www.cpan.org/authors/id/S/SF/SFINK/parrot-0.0.11.tar.gz>, or
join the party by getting the latest CVS checkout by following the
directions at <http://dev.perl.org/cvs/>.
Enhancements in 0.0.11 include:
- Executable output
- Dynamic PMC registration
- Trial exception system
- Beginnings of object system
- Iterators
- Ordered hashes
- I/O system improvements
- References
- Documentation for basic PMC types
- IMCC support of Parrot Calling Conventions
- Runtime loading of chartypes (and other string improvements)
- Conditional breakpoints
- Dramatically accelerated sweeps for finalizable objects
- Small PMCs (PMCs split into core and extensions)
- Loadable bytecode packfiles
- Constant PMCs
- Sub variants that deal with the stack correctly
- Switched runops core
- Line numbers in warnings
- Environment access
- Many documentation cleanups
- Conversion to CPS style!
- BASIC debugger and many other wacky features
- Filename, line number parsing support in IMCC
If you would like to join in the fun, see
<http://lists.perl.org/showlist.cgi?name=perl6-internals>, with
archives at
<http://archive.develooper.com/perl6-internals%40perl.org/>. All
discussion occurs on the perl6-internals mailing list. Start from
<http://www.parrotcode.org/> for information on all Parroty things.
Our immediate future plans include exceptions and objects, so now's a
good time to jump in if those things grab you.
(Oh, and I was kidding about the bread maker.)
Er, not yet. I was supposed to test the crap out of it, and then came
the feature freeze on top of a couple tests in my classes, um, the
school kind :-). I'll have it ready pretty soon.
Luke
Umm... I was talking about 'sweep 0'. Yeah, that's it!
(oops)
I've updated the native tests and the release instructions.
Could you repeat step 8 please.
leo
Damn.
Can't just do that, though, because PAUSE won't accept submissions
with duplicate filenames.
So would people prefer 0.0.11.2 or 0.0.12? (0.0.12 would improve the
average spacing between releases!)
> Can't just do that, though, because PAUSE won't accept submissions
> with duplicate filenames.
>
> So would people prefer 0.0.11.2 or 0.0.12? (0.0.12 would improve the
> average spacing between releases!)
Or bribe^Wcontact Andreas directly
Not sure. I don't really like either.
Nicholas Clark
Yep, I'm trying that route too.
> So would people prefer 0.0.11.2 or 0.0.12? (0.0.12 would improve the
> average spacing between releases!)
Either way, an updated ChangeLog could be useful.
-- c
If you're suggesting replacing the current version on CPAN it might not
be the best idea considering people have probably downloaded it
already. Best thing would be to bump up the version number, I'd go for
0.0.12.. but then - what's it's name gonna be? ;-)
-Steve
Mmm. Good point.
But part of me actually prefer the more crazy sounding 0.0.11.2, given that
it's effectively the same release.
Then again, they're only numbers, and it's not like they are a finite
resource.
Nicholas Clark
> I know what BASIC means, but what the hell is a PCM and what is a IMCC
> supposed to mean? And what is a CPS? The FAQ doesn't cover this...
You mean PMC probably, anyway, these are not really frequently asked
they are already answered:
$ find . -name '*.pod' | xargs egrep -l 'CPS|PMC|IMCC'
[ a very long list of docs snipped ]
> Best wishes,
HTH
leo
That's PCM. PMC is Phillip Martin Cozens, my father.
--
Will your long-winded speeches never end?
What ails you that you keep on arguing?
-- Job 16:3
And so has Parrot-0.0.11.1, for those of you who want correct native
bytecode tests!
http://cpan.perl.org/authors/id/S/SF/SFINK/parrot-0.0.11.1.tar.gz
Hmm... for symmetry, I'm now thinking I ought to have called it
parrot-0.00.11.1.tar.gz.
Heh. I just went down the same road, and came to the same conclusion.
For the casual observers: The problem is that those patches to allow
four-element version numbers are decidedly nontrivial. The immediate
failure is lib/Parrot/BuildUtil, which aborts Configure.pl because it
insists on seeing 3-part version numbers. The next failure is
ops2c.pl, which uses Parrot::OpsFile to tell it the decomposed parts
of the version string -- major, minor, patchlevel. And it appears that
those three values are stored in the bytecode, and I'm guessing that
the value 1.2 will not fit very comfortably into an integer field.
So even if we wanted to allow 4-digit version strings, it's too much
of a change to make while packaging up a release, so it's much easier
to just say the version is 0.0.11 and be done with it. Or if you
really want proper versioning, 0.0.12.
If we got out of this silly "version 0.0" hole, then we wouldn't need
to be so hung up about the stupid patch level.
A parrot-0.0.11.2.tar.gz is now staggering drunkenly towards CPAN,
using VERSION=0.0.11. I even tested it this time. If people want
0.0.12 instead, I can do that too.
Argh.
Only if it has objects and exceptions and moon-on-a-stick :-)
> Argh.
Thanks for all your toils in getting a release out.
Nicholas Clark