[sv-cc] Revised 265 uploaded

Hi All,
 
I reviewed the discussion we had last meeting (objectively) and then
evaluated the work/instability involved if we were to remove "type" as a
compromise (both 31 and 28 would be victims), it seems to me the changes are
quite localized and in fact touch the same areas of the proposal already.
That said, in order to ensure unanimity and address all the concerns raised
I opted to upgrade it to take the comments (that Francoise mainly made) last
time into account of course at the cost of some backward incompatibility
with tools supporting this API, but probably the code is bloated anyway with
the 2 needlessly navigation VPI of 31 and the direct data access VPI of 28.
 
Removing type, caused a clash with vpiProperty of course so I added Inst on
there and then also to sequence for consistency, the result is a good deal
of the VPI figs (sequence inst/property inst) would remain unchanged, and
gladly "inst" is back and "property" is gone ... now that I've done the work
I sorta like it, and as I said the instability of making these changes late
in the game is fairly localized and not as bad as I had initially surmised !
(who cares about backward compatible as long as it is "right", right ??
:-)!).

I uploaded the file, called SV_LRM_265_new.pdf . [Why is it of larger size
even though it is simpler ? I disabled compression and/or MS word keeps
track of every single thing I ever did !]

** I also found an extra reference to the attempt info struct in
sv_vpi_user.h that I incorporated.

** Please run through this with other sets of eyes and let me know if any
bugs. In theory this is the best/simplest version, easy to digest ...

** Michael this should make upgrade of 158 a bit easier, look through 265
towards the end and see if you can replicate the changes as well... I think
that's best to avoid races in the fixes ...

Thx.
-Bassam.

--
Dr. Bassam Tabbara
Architect, R&D
Novas Software, Inc.
(408) 467-7893