RE: [sv-cc] What time is returned from an after delay callback

My doubt was about more basic concept: interpretation of time during
callback registration. When I register callback @100 with time set to
200 then the callback occurs @200 or @300? (time absolute or
relative?)Only cbAfterDelay has clear concept due to "after" keyword in
its name - time is relative but other callbacks are not so clear.
 
Returning time during callback execution is another issue.

________________________________

From: owner-sv-cc@server.eda.org [mailto:owner-sv-cc@server.eda.org] On
Behalf Of John Shields
Sent: Wednesday, March 12, 2008 5:42 PM
To: sv-cc@server.eda.org
Subject: [sv-cc] What time is returned from an after delay callback


Hi,

We discussed a question from Krzysztof Konopko today about time related
callbacks. We agreed that a Mantis item is needed and that there was no
time to clarify it in the spec. Our sense was that the callbacks should
return absolute time. We though that VHPI had specified this, but could
not confirm it. The entire model for callbacks was more rigorously
specified in VHPI.  We should adopt it's design unless we feel there is
a conflict somewhere.  In this case, it is specified that any callback
that returns time, returns the time the callback triggered, i.e.
absolute time.  In 19.2.1 of 1076, note:

If the VHPI program registering an object callback provides in the time
member of the callback data structure
a value other than NULL, the tool, upon triggering the callback
function, provides in the time member
of the callback structure passed to the callback function a pointer to a
time structure representing the time at
which the trigger event occurred. The tool does not dereference the
value provided by the VHPI program in
the time member of the callback data structure. If the VHPI program
provides the value NULL in the time
member of the callback data structure, the value of the time member of
the callback structure passed to the
callback function is NULL.

We should add this to the initial mantis item.


Regards, John

-- 
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.