[myhdl-list] Clump'n and Lump'n

[Christopher F. <chr...@gm...>]

Hmmm, browsing the internet (instead of being focused and disciplined) I 
ran across this article

http://www1.cse.wustl.edu/~jain/cse567-08/ftp/fpgaprog/index.html#_Toc215239805 
.

The interesting point that caught my attention, was that MyHDL was 
clumped together with the C-based tools.  The author categorized MyHDL 
with ImpulseC, HandelC, SystemC, and JHDL.  The author dubbed these 
languages "Adapted Sequential HDL Programming Languages" (ASPL).  The 
goal of the study was to measure ASPLs against THDL (traditional HDLs 
i.e. Verilog/VHDL).  But I don't see any results for the proposed 
experiments.

Then the author proposes a method to measure the languages effectiveness 
based on :
   1. Language Acquisition [LA](time to learn the language, given??)
   2. Programming Efficiency [PE] (time to implement and debug design)
   3. Operational Efficiency [OE] (resources used)
(see the link for more information on the metrics)

These are tricky and somewhat subjective metrics (as the author states).

Anyone else have experience with the C/java based HDL languages?  How 
was the experience vs. MyHDL?

On a scale 1-3, 1 being highest/best how would you rate the metrics 
outlined in the paper? (The metrics are mainly time and resources, a 
lower value in time and resources are better, hence 1 being highest, 
lowest score wins!).

          MyHDL | JHDL | Verilog | VHDL | ImpC | HanC | SystemC | SV
1. LA
2. PE
3. OE


.chris