Talk:Hardware description language

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing (Rated Start-class)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.

Timing question[edit]

"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)

Introduction and making sense[edit]

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)

Well, since this is listed under Category:Specification_languages, VHDL would probably be better described as a specification language and/or a modeling language in the introduction than as a programming language. --jwilkinson (talk) 03:15, 21 December 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.
--Qwerty0 (talk) 20:26, 9 February 2011 (UTC)

This topic should be extremely difficult for an ordinary user to understand. It is used only by engineers who want to run chip prototypes in a simulated environment. HDL is extremely important, but of absolutely no interest at all to anyone but hardware and software engineer involved in chip design and simulations. HDL is the generic, and VHDL is one specific instance of the generic just as Verilog is, so VHDL is not a better description. And no, HDL is not at all for layout or printer input. It is entirely for run time characteristics, and there are flavors for analog, digital, and mixed signal. It is not at all like html as compared to Java because it has nothing to do with appearance or layout. It has to do with run time characteristics in simulated environments, and should be thought of as input to a software breadboard.

  Kirk Augustin, introduced to HDL at Analogy before it was bought out by Synopsys.  — Preceding unsigned comment added by (talk) 22:00, 15 November 2015 (UTC)