Yeah. Somehow, we need to recruit some of the list members to take charge of documentation. They would spend their time asking the developers questions, basically, and writing about what the developers explained. Anyone? :)
Are there any equivalents to Doxygen for Verilog? Or, even better, a LaTeX "plugin" like lhs2tex? That would probably be an easy solution. I, for one, think it is much easier to understand my code as I am writing it if I add comments along the way, so we might as well have those comments morph into the documentation. If a developer writes code, it is their responsibility to comment it carefully. Once a LaTeX file is generated, volunteers from the community can spice up the documentation.
This all relies on the fact that there is a documentation generator for Verilog. Does anybody
know if such a thing exists? _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
