<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 19/10/2025 18:02, Hairy Pixels via
fpc-devel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGsUGt=Q-O0_Ok2a3prYpLnCsNBM0qBzfyOR5xGCmJekX2FEvQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Oct 19, 2025 at
10:50:42 PM, Martin Frb via fpc-devel <<a
href="mailto:fpc-devel@lists.freepascal.org"
moz-do-not-send="true" class="moz-txt-link-freetext">fpc-devel@lists.freepascal.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"
type="cite">
<div>Well, yes, it may be unimplemented in the parser... And
maybe that is all of it. <br>
<br>
Maybe historically it would have been a complex task to add.
Yet, currently it would seem to be that the parser just
needs to skip any amount of "dot identifier"?<br>
</div>
</blockquote>
</div>
<br>
<div dir="ltr">Ideally the parser catches syntax errors before
specialization.</div>
</blockquote>
Yes, but as you can see from my example, even if a constrained type
was checked, the sub-class that is given to specialization may
contain something different. And with nested declarations, that can
even mean that a member that is accessible via the base class, does
no longer exist in the subclass, i.e the nested type from the base
class is hidden, and the "reintroduced" type does not have the same
tree.<br>
<br>
Originally I thought, well ok, it allows better checks. But then I
discovered, that this isn't the case.<br>
<br>
</body>
</html>