<HTML>
<style> BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }</style>What I've gathered is that with the following routine:<br>
<br>
function DoSomething: Integer;<br>
begin<br>
for Result:=alow to ahigh do
<br>
if Something(Result) then exit;
<br>
end;<br>
<br>
The issue occurs if "Something(Result)" always returns False and the for-loop exits normally. While some languages and compilers will consistently set Result to "ahigh + 1" after the last cycle, this is not the case with Free Pascal, hence Result is undefined and the last value of R/EAX (which may or may not be False from the last call to "Something") becomes the function return.<br>
<br>
I'm not certain, but at the very least, if the variable used in the for-loop is still live afterwards (that is, it's read from before being written to again), a compiler warning should be thrown. If this already happens, then it might need to be modified to handle Result as a special case.<br>
<br>
Gareth aka. Kit<br>
</HTML>