However, \small{EDIF} is not completely tool-independent. It specifies a
meta-format, but the hardware components that can be used vary between
various tool and hardware vendors, as well as the interpretation of the
- \small{EDIF} standard. \todo{Is this still true? Reference:
- http://delivery.acm.org/10.1145/80000/74534/p803-li.pdf?key1=74534\&key2=8370537521\&coll=GUIDE\&dl=GUIDE\&CFID=61207158\&CFTOKEN=61908473}
+ \small{EDIF} standard. \cite[li89]
This means that when working with \small{EDIF}, our prototype would become
technology dependent (\eg only work with \small{FPGA}s of a specific
month = {Sep},
abstract = {Haskell is a great language for writing and supporting embedded Domain Specific Languages (DSLs). Some form of observable sharing is often a critical capability for allowing so-called deep DSLs to be compiled and processed. In this paper, we describe and explore uses of an IO function for reification which allows direct observation of sharing.}
}
+
+@inproceedings{li89,
+ author = {Li, W. and Switzer, H.},
+ title = {A unified data exchnage environment based on EDIF},
+ booktitle = {DAC '89: Proceedings of the 26th ACM/IEEE Design Automation Conference},
+ year = {1989},
+ isbn = {0-89791-310-8},
+ pages = {803--806},
+ location = {Las Vegas, Nevada, United States},
+ doi = {http://doi.acm.org/10.1145/74382.74534},
+ publisher = {ACM},
+ address = {New York, NY, USA},
+}
+
+% vim: set paste: