10.06.2016 Views

eldo_user

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Eldo Netlist Setup<br />

Directives Interpreted by the Eldo Parser (Default)<br />

#ifdef b<br />

c1 1 0 1<br />

#endif<br />

#ifdef a<br />

#define b<br />

l1 2 0 1<br />

#endif<br />

the first #ifdef block is ignored because identifier b is not defined until the next #ifdef block.<br />

The correct order for identifier b to be taken into account in this example is as follows:<br />

#ifdef a<br />

#define b<br />

l1 2 0 1<br />

#endif<br />

#ifdef b<br />

c1 1 0 1<br />

#endif<br />

AMS_VERSION<br />

You can make use of the predefined name AMS_VERSION in directive statements.<br />

AMS_VERSION is accepted in two formats:<br />

• The year followed by the index number, for example 2010.1 or 2012.2 (for the 12.2<br />

release).<br />

• The release version, for example 12.2.<br />

For lettered releases, specify the letter to be taken into account, for example 2012.2a or 12.2a<br />

for the 12.2a release.<br />

Note<br />

This feature only works in a netlist being run by AMS2010.1 or newer.<br />

Using a version testing pragma such as this enables using and maintaining a single library with<br />

multiple releases of Eldo.<br />

Examples<br />

An example of using predefined name AMS_VERSION in #define statements:<br />

#if ( AMS_VERSION >= 2010.2)<br />

.lstb vd1 vd2<br />

#else<br />

*versions prior to 2010.2 do not support differential LSTB<br />

.lstb vstb<br />

#endif<br />

Another example using predefined name AMS_VERSION shows you can specify different<br />

options/settings depending on the version of Eldo you are using.<br />

124<br />

Eldo® User's Manual, 15.3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!