Re: Use by copy or use by reference

Hi all,

I'm taking a few minutes to check into what I missed today.

This is from the quote by Dennis in Brian's email:

> The only issue is standard references may grow stale and not keep
> pace with what we do with them.

I do not see that as a real issue.  The thing is, we are writing
a standard that will be based on a number of other standards
including SystemVerilog.  The standard we write will be based
on those other standards as they are they day our standard is
frozen/published.  If those other standards are updated we will
have to update ours to match.  Of course, we only need to update
if the other standard changes in an area that affects us.  The
way we track is by updating.  That way it makes no difference
whether we copy or reference as long as we reference specific
versions.

As for DPI, I am not sure referencing makes much sense as we
have to modify the text since we are only supporting a subset.
Were there some ideas along the lines of referencing and then
listing the differences?

> One way around your issue, as I have seen in the past is,
> experts in the standard will author books targeted for special
> and focused needs.

I think that this is the way to go for the implementor.  It
is the job of the implementor to write the documentation for
the implementation.  I don't think it is the job of the ITC
committee to write such documentation.  We are writing a
standard.  Our focus should be to write the standard as precisely
as possible to minimize the risk of differing interpretation
leading to incompatible implementations.

Per

-- 
Per Bojsen                                Email: <bojsen@zaiqtech.com>
Zaiq Technologies, Inc.                   WWW:   http://www.zaiqtech.com
78 Dragon Ct.                             Tel:   781 721 8229
Woburn, MA 01801                          Fax:   781 932 7488