Actually, this is the REAL concern, in my opinion: Constructs
that might be mutually incompatible. I guess we all
have had problems with EDA tools which would not work
together because of any of a variety of incompatibilities.
I think previous opinions about ensuring well defined
boundaries between SID & OOVHDL might have been unnecessarily
strict: I don't see a lot of harm in writing a standard
which EXACTLY copied some well-defined constructs from
existing, approved standards, in order to ensure
unambiguous statement of the strictly OO construct
(whether the OO standard were part of a larger document
or not).
There is a very big maintenance problem divvying up
everything perfectly neatly, when citing constructs
from existing standards: If the cited standard should be
revised, the citation would become invalid. This problem
grows, as constructs become more mutually exclusive.
I guess this is an argument in favor of issuing an OOVHDL
standard as a chapter in the 1076 document.
--
John
jwill@pacbell.net
John Michael Williams