<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Am 30.10.2013 12:59, schrieb John Lee:<br>
</div>
<blockquote
cite="mid:CAMWP1+Z4GHz=UX0kT+204e701H0y-sSGec73Ky38eYCPO1tVAg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="im"
style="font-family:arial,sans-serif;font-size:13px">jonas
wrote</div>
<span style="font-family:arial,sans-serif;font-size:13px">
<div><span style="font-family:arial,sans-serif;font-size:13px">'</span></div>
It may indeed be possible to handle this in the compiler.</span>
<div class="im"
style="font-family:arial,sans-serif;font-size:13px"><br>
> What about llvm - (coming soon to fpc apparently) - would
that fix it?<br>
<br>
</div>
<span style="font-family:arial,sans-serif;font-size:13px">Not in
the least. "soon" is also a gross overstatement.</span><br>
<div><span style="font-family:arial,sans-serif;font-size:13px">'</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">What's
the size/difficulty of compiler spotting this? Suppose it
needs to be able to 'look ahead' by few statements - which
I'd thought it does already to some extent. <br>
</span></div>
</div>
</blockquote>
It's not about parsing. The code will be parsed the same
nevertheless.<br>
<br>
It would be a optimization on the resulting node tree however after
the function was parsed and before the code is generated.<br>
<br>
Regards,<br>
Sven<br>
</body>
</html>