Include files names/paths in the LRM

Nobody responded to this one first-time-around. Comments please!

The OSCI TLM-2.0 LRM includes several sections (10.2, 11.8, 11.8.1) that
refer explicitly to the directory structure of the OSCI TLM-2.0 kit. We
will want to omit most of these dependencies from the IEEE standard,
right?

However, the OSCI LRM requires applications to #include the header files
of any utilities from the tlm_utils directory, which raises the following
questions:
- Does the directory tlm_utils need to be documented in the LRM?
- Do the names of the utility source files need to be documented?
- If not, how can applications that use TLM-2.0 utilities be made portable
across implementations?

In the TLM-2.0.1 kit, the header file is named "tlm.h". This name does
not follow the convention used in SystemC, where
"systemc.h" is the old-style header that dumps all names into the global
namespace
"systemc" is the new-style header where all names are in sc_core or sc_dt

Since the TLM-2.0 header is a new-style header, by rights it should have
been named "tlm", be we need to retain the name "tlm.h" for backward
compatibility. Any suggestions?

Thanks,

John A

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