Erik Lechak wrote: > ... I decided not to continue on > the "comment the code route" because I don't like POD. And I think a > good demonstration of why I don't like it is the ops files. I am trying > to think of a polite way to introduce java and python people to the ops > files when they are a mixture of C, POD and perl comments.
Actually docs/core_ops.pod is already autogenerated from core.ops - so I don't see your point. core.ops is readable and has _all_ the information in it, what is currently needed to assemble or execute an op code. And mixture - not really, it's like a perl file: =something pod_goes_here =cut code_goes_here .... with one difference, "code_goes_here" is not perl code, but is translated by perl to generate various files, and yes, has C like semantics. Please try to read similar solutions that use m4 for such a task ... brrr. So don't care much about *.ops, their docu is already autogenerated - though the contents of the documents is a little bit hmm sparse ;-) leo
