Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: tliCRunning vs. tliCDone

tliCRunning vs. tliCDone 21 May 2009 15:35 #7601

I have a few questions regarding some of the TCI-TL functions. (This all
refers to the 4.0.1 draft.)

tliCRunning has this signature:

void tliCRunning(in TString am, in TInteger ts, in TString src,
in TInteger line, in TriComponentIdType c,
in TriComponentIdType comp, in ComponentStatusType status)

The signature of tliCAlive is equivalent.

tliCKilled has this:

void tliCKilled (in TString am, in TInteger ts, in TString src,
in TInteger line, in TriComponentIdType c,
in TciNonValueTemplate compTmpl)

tliCDone has this:

void tliCDone (in TString am, in TInteger ts, in TString src,
in TInteger line, in TriComponentIdType c,
in TriComponentIdType comp, in TciNonValueTemplate compTmpl)

It's similar to tliCKilled, but not the same: the "comp" parameter seems
to be a mistake. (No parameter description for it.) Correct?

More importantly, what's "compTmpl"? Is this supposed to represent "any
component", "all component" or a specific component, as in the
corresponding expressions? (I don't see any actual templates in the
description of the killed and done operations.) If so, why are tliCAlive
and tliCRunning different? Also, what the call patterns to tliCAlive
supposed to be for any component.alive and all component.alive, for
instance?

--
Regards,
Mike
The administrator has disabled public write access.
  • Page:
  • 1

FacebookTwitterGoogle BookmarksRedditNewsvineTechnoratiLinkedin