On Thu, 23 Feb 2006, William Killian wrote:

> There is no
> compiler that can take a function and not generate the return or the 'as
> if' version of return without guidance.

I've been using one for years that does it.  I've never had a function
that mysteriously failed to return.  And I'm sure this compiler is not
unique.

> Such a compiler would have to
> be pretty good to identify a function that will never return but know it
> is not a mistake.

I don't see it as such a difficult problem.  If the last statement of
the function branches to the beginning of the function, and there are
no breaks/gotos in between that branch beyond the end of the outer
loop, why would the function need a return?

--
John W. Temples, III
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist