Hi,
Sorry for delay in getting to this - been working on-site with $JOB for
a while. Comments and questions below, but please see r15001.
Leopold Toetsch wrote:
2) How should we handle changes to the core Parrot library (mostly PMCs,
but also consider anything we promise is available)?
Am Montag, 23. Oktober 2006 18:31 schrieb Jonathan Worthington:
1,5) same + range of indices
Will a dynamic character set or encoding library that we load not
possibly contain more than one character set or encoding and therefore
need a range of indices too? I have gone with this for
Bernhard Schmalhofer wrote:
One thing that I noticed is the naming of the new field UUID.
||| The UUID is |
||| computed by applying the hash function specified
in|
||| the UUID type field over the entire packfile
not |
||
Leopold Toetsch wrote:
Indeed. But we probably want to have an UUID to identify
loaded .pasm/.pir/.pbc to avoid loading duplicates.
The UUID as proposed was intended for that; I just hashed up the
definition in the PDD. Er, no pun intended.
As a side note: distinct PBC segments for
Jonathan Worthington schrieb:
Hi,
I've checked in the proposed bytecode PDD and also most of the changes
that I discussed with Allison earlier today. Feedback on it would be
greatly appreciated.
One thing that I noticed is the naming of the new field UUID.
||| The UUID
Am Donnerstag, 5. Oktober 2006 23:04 schrieb Bernhard Schmalhofer:
Shouldn't this field be renamed to something like 'checksum' ? The term
'UUID' already has a specific meaning, http://en.wikipedia.org/wiki/UUID.
Indeed. But we probably want to have an UUID to identify
loaded .pasm/.pir/.pbc
Am Freitag, 29. September 2006 01:39 schrieb Jonathan Worthington:
Hi,
I've checked in the proposed bytecode PDD and also most of the changes
that I discussed with Allison earlier today. Feedback on it would be
greatly appreciated.
Great work, thanks.
A couple of open questions
I just got off the phone with Jonathan Worthington. At YAPC::EU he
agreed to draft a PDD for Parrot's bytecode file format. He has done a
fantastic job. He's checking it in now, so everyone will have a chance
to comment. The PDD incorporates a handful of important changes that
have been
Hi,
I've checked in the proposed bytecode PDD and also most of the changes
that I discussed with Allison earlier today. Feedback on it would be
greatly appreciated.
One of the areas that it would good to have some input on, even if it's
just a yes, that's sane, is versioning. The current
