ACM Home Page
Please provide us with feedback. Feedback
CONLAN: a formal construction method for hardware description languages: language derivation
Full text PdfPdf (878 KB)
Source AFIPS Joint Computer Conferences archive
Proceedings of the May 19-22, 1980, national computer conference table of contents
Anaheim, California
SESSION: Computer architecture table of contents
Pages 219-227  
Year of Publication: 1980
Authors
Robert Piloty  Technische Hochschule Darmstadt, FR Germany
Mario Barbacci  Carnegie-Mellon University, Pittsburgh, Pennsylvania
Dominique Borrione  Universite de Grenoble, Grenoble, France
Donald Dietmeyer  University of Wisconsin-Madison, Madison, Wisconsin
Fredrick Hill  University of Arizona, Tucson, Arizona
Patrick Skelly  Honeywell, Phoenix, Arizona
Sponsor
AFIPS : American Federation of Information Processing Societies
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 2,   Downloads (12 Months): 5,   Citation Count: 2
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1500518.1500551
What is a DOI?

ABSTRACT

A CONLAN document has significance only if it is read by a person or machine. That reader (environment) is required to use available facilities to respond to and interact with the document. It must provide the type checking mechanism. It must record the names of defined and declared items and provide the data base they require. It must record signal values. From such records, it can determine facts of importance to continued document evaluation. "System interfaces" are prescribed environment responses, not formally defined via CONLAN syntax.



Collaborative Colleagues:
Robert Piloty: colleagues
Mario Barbacci: colleagues
Dominique Borrione: colleagues
Donald Dietmeyer: colleagues
Fredrick Hill: colleagues
Patrick Skelly: colleagues