"Synthesizers generally ignore the expression of any timing constructs in the text. Digital logic synthesizers, for example, generally use clock edges as the way to time the circuit, ignoring any timing constructs. "
If synthesizers ignore the timing constructs, then why are they added at all to an HDL circuit description? Thanks, -Abdull (talk) 16:55, 7 February 2010 (UTC) VHDL was originally a description language for hardware designed in a more traditional way, ie schematic capture. It was only later used for synthesis. VHDL is also frequently used for non-synthesis purposes such as test benches where the full scope of the language can be used. Hope that helps!Hardyp3 (talk) 14:56, 12 September 2013 (UTC)
Just making it clear to anyone working on this article that the introduction doesn't describe what a hardware description language is to anyone who doesn't already know what a hardware description language is.
When you see the term "hardware description language" you first think of some very basic questions such as "What does that mean?" and "A normal programming language is compiled into instructions telling a computer what to do. What is this 'compiled' into and what executes the instructions?" and "Is it executed by a computer or printer displaying a 3D diagram or blueprints?" or "Does it directly tell something like a 3D printer what to create?"
None of these questions are answered by the introduction. Instead it seems to assume you know what it does, then describes it further with more jargon. --Qwerty0 (talk) 11:51, 7 July 2010 (UTC)
Ok thanks, so I think I get it now. It's more like HTML than Java. It's just a formal language for describing something? I'd still suggest clarifying that in the introduction. If I knew enough to make sure it'd be accurate, I'd go for it myself. If at some point I've learned that much, I'll take a crack at it.