RE: [sv-cc] proposal for #482 revised

Yes, Sachi, proposal #533 also removes the vpiAccess
property from class var.  And it isn't really the class
var for which vpiVisibility matters anyhow, but the
variables inside classes.

I'm trusting that Stu won't get confused by having
both proposals get rid of vpiAccess from 32.22.

Regards,
Jim V.

--------------------------------------------------------- 
James H. Vellenga                            978-262-6381 
Engineering Director                   (FAX) 978-262-6636 
Cadence Design Systems, Inc.         vellenga@cadence.com 
270 Billerica Rd 
Chelmsford, MA 01824-4179 
"We all work with partial information." 
---------------------------------------------------------- 
  
 

] -----Original Message-----
] From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On 
] Behalf Of Sachchidananda Patel
] Sent: Thursday, April 14, 2005 2:31 PM
] To: sv-cc@eda.org
] Subject: [sv-cc] proposal for #482 revised
] 
] I uploaded a new proposal for #482.
] Apart from changes discussed in the last meeting I found one more
] issue with class var, i.e. the property vpiAccessType.
]  From the Notes, it appears that it was intended for what is 
] now called
] visibility (vpiVisibility).
] Rather than changing it to vpiVisibility, I removed it because the
] variable diagram has it already. Let me know your comments.
] 
] regards,
] -sachi
] 
]