"
Team:Berkeley Software/Eugene Implementation
From 2009.igem.org
Adam z liu (Talk | contribs) |
Adam z liu (Talk | contribs) |
||
| Line 7: | Line 7: | ||
<li>[[Team:Berkeley_Software/Eugene#Examples|Examples]] | <li>[[Team:Berkeley_Software/Eugene#Examples|Examples]] | ||
<li>[[#Implementation|Implementation]] | <li>[[#Implementation|Implementation]] | ||
| + | <li>[[Team:Berkeley_Software/Eugene_Results|Results]] | ||
<li>[[Team:Berkeley_Software/Eugene_Results#Conclusions|Conclusions]]</td> | <li>[[Team:Berkeley_Software/Eugene_Results#Conclusions|Conclusions]]</td> | ||
<td>          </td> | <td>          </td> | ||
Revision as of 20:48, 19 October 2009
| Content:
|
 |
Implementation
Figure 1: Eugene Flow Diagram
Header File Creation
Header files give the language the functionality to access many already predefined Parts in the databases. For the purpose of convenient data exchange over the Internet, XML could be used to read information from a database. Then the data is converted into Eugene syntax to represent the header files. As a result the language definitions are not just abstract statements but are tied to existing designs. There are three main header files: PropertyDefintion.h, PartDefiniton.h and PartDeclaration.h shown in Figure 1.
Eugene Main File
The main .eug file can include the header files, which need to be specified at the top:
include PropertyDefintion.h, PartDefinition.h, PartDeclaration.h;
The main file will generally consist of custom Part definitions/declarations, device constructs, rule implementations and control statements.
