Related articles |
---|
call tree alin.arsu@gmail.com (Alin) (2006-05-09) |
Re: call tree DrDiettrich@compuserve.de (Hans-Peter Diettrich) (2006-05-11) |
From: | Hans-Peter Diettrich <DrDiettrich@compuserve.de> |
Newsgroups: | comp.compilers |
Date: | 11 May 2006 01:52:51 -0400 |
Organization: | Compilers Central |
References: | 06-05-029 |
Keywords: | analysis |
Posted-Date: | 11 May 2006 01:52:51 EDT |
Alin wrote:
> I have a hard question (at least for me)...
> "There are API calls which are not allowed to be called in certain
> constrains and must be identified".
Do you want a static (control flow) analysis or a dynamic analysis?
> If "alternates" are taken, based on if I have:
> constrainStart();
> constrainStop();
> API1();
> constrainStart();
> constrainStop();
>
> and this shown the code is OK....
I'd wrap such API calls like this:
if (condition) {
//write message to the log, if desired
> constrainStop();
> API1();
> constrainStart();
} else API1();
A global condition flag can be maintained by constrainStart/Stop.
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.