<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-9"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 2010-05-31 17:21, Krisztián Nagy wrote:
<blockquote
cite="mid:AANLkTinfQt7mhmxJOiQGijZARzSk-4cqRpP_ZbxHgjRT@mail.gmail.com"
type="cite">
<div>
<div><br>
</div>
<div>"<span class="Apple-style-span"
style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">You'll
have competing products one pulling one way, the other pulling another."</span></div>
<div><span class="Apple-style-span"
style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">I'm
not sure I understand you correctly. If you were talking about the two
parsers then this makes no sense to me as we are going to have two
parsers both sticking to the same "official" free pascal specification,
one optimized for high speed compilation the other for general purpose
use. These are not competing products and even less pulling each other
different ways.</span></div>
</div>
</blockquote>
If we had an comprehensive official specification or any chance of
getting one in near future, I'd definitely agree with you.<br>
<br>
But, there isn't one. <br>
<br>
And, AFAIK, there has never been one (at least in the last 20 years)
that has been adhered to in every detail. Each implementation has been
a subset with more or less extensions. Source code has as usual been
the only complete definition.<br>
<br>
Could we use the parser(s) to produce specifications too, I wonder.<br>
<pre class="moz-signature" cols="72">--
Cheers,
Adem</pre>
</body>
</html>