[sv-cc] RE: Mantis item 2226: Value change callback changes

Jim,

 

I can see your point about separating the interests.  My concern is that
we unified the dynamic object model by identifying a use case that was
important and basic - logging.  In so doing, we aimed to enable
effective logging for a broader subset of SV.  We would not have a clear
focus on the lifetimes and tracking them nor an object identifier in the
form it is in without this kind of thinking.  So, if parititions the
extensions to cbValueChange, perhaps we should add other vestiges of
this thinking as well.  The problem with the result comes in 2 parts.
First, in what is left for this proposal, it willl be harder to
demonstrate its value and purpose.  Secondly, we do not serve some clear
interests in doing this task.

 

I don't mind partitioning it out to another Mantis item.  I wrote with
an eye toward correcting some of the narrowness in terminology for
cbValueChange and broadening it.  But it also is amenable to limits, as
you say.  Let's review the proposal for everything but this aspect.
Then can we consider it, whether it is moved to another item or not?  We
talked about all the limits once and this is a first attempt to respond
to them.  I'd have some hope for it.

 

Regards, John

 

________________________________

From: Jim Vellenga [mailto:vellenga@cadence.com] 
Sent: Thursday, March 20, 2008 6:27 AM
To: Shields, John; sv-cc@eda.org
Subject: Mantis item 2226: Value change callback changes

 

John and the rest of the team,

 

I strongly recommend against including cbValueChange changes as part of 

the handle and object lifetime Mantis item.  I am sure that if we do, 

there will be enough effort at clarification of the limits, and even 

the wording, that we will not be able to finish the Mantis item on 

time.  I can see already several problems with wording in the existing 

proposals, and questions that we'd have to work through the answers to.

 

Let's keep the focus on handle and object lifetimes in an effort to get 

at least this proposal through.

 

Regards,

Jim Vellenga

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

 

	 

	
________________________________


	From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf
Of Shields, John
	Sent: Wednesday, March 19, 2008 10:20 PM
	To: sv-cc@eda.org
	Subject: [sv-cc] updated mantis item 2226 with proposal

	Hi,

	 

	This is detailed proposal of the information model for dynamic
objects.  There are changes to clause 36 and 37 in 2 documents.

	 

	Regards, John Shields

	Mentor Graphics, Inc.

	
	-- 
	This message has been scanned for viruses and 
	dangerous content by MailScanner <http://www.mailscanner.info/>
, and is 
	believed to be clean. 


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