RE: Version number macros

John,

sorry to insist... I perfectly understand that SYSTEMC_VERSION_* macros are a way to identify a specific implementation version within a vendor's lineage.

However, I do think that applying the same reasoning to the TLM_VERSION_* macros does neither seem to be useful nor logical. Whereas it is true
that TLM itself can be implemented "differently" by each vendor (to add specific instrumentations, etc.), particular implementations details
can already be identified through the SystemC version macros, and it is important to be able, say, to rely on TLM_VERSION_MAJOR being 2 or greater
to be sure that TLM-2 itself is implemented. Isn't it?

Jerome

From: owner-systemc-p1666-technical@eda.org [mailto:owner-systemc-p1666-technical@eda.org] On Behalf Of john.aynsley@doulos.com
Sent: Monday, October 04, 2010 6:14 PM
To: systemc-p1666-technical@eda.org
Subject: RE: Version number macros

To answer Jerome, sure, the actual choice of version numbers is implementation-defined. The standard only defines the formal structure. The OSCI simulator follows a specific lineage of version numbering. Other vendors may base their versions on the OSCI numbering or may do their own thing. These strings relate to the implementation itself, NOT to the version of the IEEE standard the implementation claims to support. That would be presumptuous!

Does that work?

John A

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.