Hi all, thanks to Novas who provided software we successfully integrated their nLint design rule checker into our CVS system. This new tool helps designers to write better quality HDL code by performing source code checks to ensure conformance with design rules such as synchronous design, clocking scheme, naming conventions, and testability. We configured nLint according to OpenCores design guidelines. This way we will get common coding style for all cores stored in the CVS. So how does new system work? All you have to do is to enable nLint for your project and you will get email report each time you will import/change some verilog/vhdl files in CVS. You can enable nLint on Admin::Properties page of your project by adding Service::Lint property to project properties. For more information about nLint visit Novas web site: http://www.novas.com/Products/nLint/ regards, Miha

Aloha! Quoting Miha Lampret mihal at opencores.org>:

Extremely cool. Good job Miha et al! Also thanks to Novas for providing the
tool. This is a good step towards high quality cores.


--
Yours

Joachim Strombergson
-------------------------------------------------------------------------------
InformAsic AB
-------------------------------------------------------------------------------

Most excellent. For EXISTING cores will the nLint output be made publicly available?

You might get some people interested in doing valuable clean-up work if it were.