Hi all,
me again! I found a few things in PDD13 - Parrot Bytecode which need
work. Again, this is just an email to start of discussion and to then
generate any refinements necessary for a complete(d) design.
=item Key Constants
Within this section there is the todo item:
{{ TODO: Figure out slice bits and document them here. }}
So, we need to work out how slice bits should look and then document
(and eventually implement) them.
=item Fixup Segment
Here there is the todo item:
{{ TODO: I think label fixups are no longer used. Check if that is so. }}
Are fixup labels no longer used? Do we need to document the status of
fixup labels here if they aren't used anymore?
=item Annotations Segment
Here's the todo item with context:
An annotation groups table, used to group together annotations for a
particular HLL source file (an annotation group starting clears all active
annotations, so they will not spill over between source files; it also
allows for faster lookup of annotations).
{{ TODO: Does it clear all annotations, or all annotation groups? }}
=item Packfile PMCs
There's quite a long todo item within this section. Here's the
relevant text with some context:
A packfile will be represented in memory by Parrot as a tree of PMCs. These
will provide a programatic way to construct and walk packfiles, both for the
Parrot internals and from programs running on the Parrot VM.
{{ TODO... QUESTION: Will the CStruct PMC make it into Parrot? If so, we
may want to change the interface of these PMCs to take advantage of it.
ANSWER: Yes it will (most likely with a different name), but it needs to
be prototyped first. Do you want to hold off on implementing the
bytecode changes until it's available? I say go ahead and implement now,
then revise when the new PMC is available. }}
It looks like the answer is already known. This just needs to be
documented properly then doesn't it? Have the bytecode changes (which
ones?) been implemented? Has any prototyping been done?
=cut
That's it at present I think. I've still got Objects (PDD15) and
Exceptions (PDD23) to go through yet, but I won't get to there before
this weekend. Exceptions have already been designed haven't they? So
we don't actually need to discuss this PDD, right?
Many thanks for reading my emails! I hope to get back to just
committing code soon...
Paul
