3 ms·

>Avoid ever referring to it as code I tend to call verilog or VHDL "VHDL Hardware Specification". Try to make it sound as un codelike as possible After all VH

by gte910h 16y ago

>Avoid ever referring to it as code I tend to call verilog or VHDL "VHDL Hardware Specification". Try to make it sound as un codelike as possible After all VHDL was the way that military contractors came up with to specify their parts to the Govt in case they went belly up.

harnhua 16y ago
As I was trained in Verilog and know little about VHDL, to be honest, I'm not quite sure why "code" is inappropriate. But thinking about your(blasdel's and gte910h's) comments, I'm beginning to see how error-checking can and should be different for FPGA development.
- blasdel 16y ago
  Because neither Verilog nor VHDL is code. HDL is a slightly handwavey description of the graph of a machine, not something that runs on a machine. You have wires, not variables: real physical wires connecting gates and LUTs. Since you're dealing with real-world electrical current, each wire can be in one of four binary states (null, low, high, grey). There's no concept of time beyond the speed of light itself unless you deliberately bind a clock line from the outside to a wire.