Dan -- > >I've made core.ops contain op documentation, and I'd like to make it > >the official place where ops are documented. > > Nope. :) > > parrot_opcodes.pod is essentially a design document. It's the documentation > that describes the abstract machine that the code in the source implements. > I want them separate on purpose. If, at some point, someone comes along and > decides that we're a bunch of clueless fsckwits and they can do a better > job implementing Parrot, they work from parrot_assembly.pod.
Understood. OK. I'll simply make sure that where the design doc has info we don't have in core.ops, I copy it over there for folks that look for docs related to *our* implementation of the standard. > If you want a real-world sort of example, it'd be like tossing out RFC821 > and RFC822 because the source for sendmail has all the documentation on how > it works embedded in comments in its source. 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 \_____________________________________________________________________/
