|
From: Cary R. <cy...@ya...> - 2008-04-21 17:32:55
|
A quick update on this.
I have the basics working. I am assuming a forever and while with a constant true expression should also check for infinite loops. I still need to add function and task call statements and the switch statement which is just an extended conditional still need to be coded. I also have a couple questions about how the indeterminate messages should be displayed.
Should we make the indeterminate case, may be an infinite loop, only display a message when the appropriate -W (inf_loop) flag is given? Do we want this included in the -Wall case? My guess is that we probably do not since this is a possible warning not a true problem that should be fixed. It's the limitations of the checks that is preventing us from making a true determination of the state. I do not believe we should try to truly determine this either. There is way too many things that would need to be looked at and evaluated for a minimal return.
Once this is completed we will need to have an explanation on the wiki that covers how to interpret what a possible infinite loop means. It may also be nice to have a small section in the manual that gives the basics.
Cary
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
|