On Wed, 19 Dec 2001, Alex Gough wrote:
> Much of parrot_assembly.pod seems out of date, or raises interesting
> questions:
>
> Are we going to bother with NAMESPACEs and SUBs in assembler?
Yup. We just haven't gotten there yet.
> Is it worth keeping documentation for (implemented) opcodes in this
> file, when they can be generated from pod in *.ops files as required?
Yes. Parrot_assembly.pod's the canonocal documentation. Anything that's in
core.ops is a nice extra.
> Of those listed in parrot_assembly.pod, there are some which have
> not yet been implemented:
We need to work on those. I appreciate the list.
Dan
