Dan -- I've made core.ops contain op documentation, and I'd like to make it the official place where ops are documented. That means I'd like to make sure there is nothin documented in docs/parrot_assembly.pod that isn't equivalently or superiorly documented in core.ops and then remove the duplicate information from docs/parrot_assembly.pod, replacing it with a pointer to the docs/core_ops.pod (which is autogenerated from core.ops via docs/Makefile).
Generally, I'd like .ops files to be self-contained op libraries, and that means they should contain all the op documentation we need. Then, I'd like to take the documentation from docs/parrot_assembly.pod that is left, and integrate it into assembler.pl, and put an entry in docs/Makefile to extract the POD from assembler.pl to docs/assembler.pod automatically. Is this acceptable to you? Regards, -- Gregor _____________________________________________________________________ / perl -e 'srand(-2091643526); print chr rand 90 for (0..4)' \ Gregor N. Purdy [EMAIL PROTECTED] Focus Research, Inc. http://www.focusresearch.com/ 8080 Beckett Center Drive #203 513-860-3570 vox West Chester, OH 45069 513-860-3579 fax \_____________________________________________________________________/
