On Aug 5, 2010, at 10:26 PM, Jordy Rose wrote: > 2. Evaluations. First checker to claim the statement wins, and it can > create multiple ExplodedNodes. (Ex: EvalCallExpr, EvalNilReceiver)
I'm of mixed feelings on this one, and I've contemplated how to get rid of it. Ultimately we probably need it for simulating the actual effects of a function call, but there isn't a clear design for how to reconcile multiple Checkers that implement EvalCallExpr. _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
