<html><body><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">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. FPC has an undefined type so upon encountering this you would be an "undefined sub tree expression parser" which could handle all possible expressions which originated from the identifier.</div><div dir="ltr"><br></div><div dir="ltr">FPC just stores the raw tokens so all the compiler really needs to know is where the start and end of the generic type/proc are.</div><div dir="ltr"><br></div></body></html>