Verilog Coding Guidelines

I wrote a Verilog Coding Guidelines doc. Comments are welocome:

h--p://bknpk.no-ip.biz/MiscellaneousHW/MiscellaneousHW.html

 

[gabor]

On Jan 3, 11:20 am, beky...@gmail.com wrote:

I wrote a Verilog Coding Guidelines doc. Comments are welocome:

h--p://bknpk.no-ip.biz/MiscellaneousHW/MiscellaneousHW.html

Unless I missed something, it seems your only guideline
is to separate combinatorial and registered equations.

I personally don't agree that this helps readability.
In you small example there was very little difference
in readability between the two versions, but in a
typical Verilog module your method would very likely
place the combinatorial logic well off the screen
requiring a lot of scrolling to see what is going on.
Your use of "qi" as an intermediate signal name
doesn't help this either. Perhaps if you had
called it "a_and_b" I wouldn't need to scroll
around to find the code.

Secondly I don't see the point in creating a
Verilog coding style based on the bugs of a
particular simulator. It makes much more sense
to use a better simulator or fix the bugs.

Just my 2 cents,

Gabor