mirror of
https://github.com/RGBCube/serenity
synced 2025-05-31 11:28:12 +00:00
b74df136fe
Due to the way expression parser is written, we need to resolve the ambiguity between member access operators and dots used for punctuation during lexing. The lexer uses a (totally bulletproof) heuristic to do that: whenever '.' is followed by ' ' or '\n', it is considered a dot and member access otherwise. While it works fine for prettified test cases, non-prettified files often lack enter after a trailing dot character. Since MemberAccess will always be invalid at that position, explicitly treat trailing dot as a part of punctuation.
19 lines
668 B
XML
19 lines
668 B
XML
<!DOCTYPE inline_dtd[<!ENTITY nbsp " ">]>
|
|
<specification>
|
|
<emu-import>
|
|
<emu-clause id="1">
|
|
<h1><span class="secnum">1</span> The Celestial Object</h1>
|
|
<emu-clause id="1-1">
|
|
<h1><span class="secnum">1.1</span> Abstract Operations</h1>
|
|
<emu-clause id="1-1-1" aoid="Foo">
|
|
<h1><span class="secnum">1.1.1</span> Foo ( <var>a</var> )</h1>
|
|
<emu-alg>
|
|
<ol>
|
|
<li>Return <var>a</var>.<var>[[b]]</var>.</li>
|
|
</ol>
|
|
</emu-alg>
|
|
</emu-clause>
|
|
</emu-clause>
|
|
</emu-clause>
|
|
</emu-import>
|
|
</specification>
|