At 05:16 PM 10/15/2001 -0400, Gregor N. Purdy wrote:
>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.
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.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
