Re: Scan "=<<" as something useful
Rich Neswold <[email protected]>
| Newsgroups | gmane.comp.lang.erlang.patches |
|---|---|
| Message-ID | <CAGT4q5qQb4tiqrtP=DsFg9gXCFg1PsMibwry6+MPvCv_oLA7fw@mail.gmail.com> |
On Mon, Jun 10, 2013 at 9:50 AM, Raimo Niskanen < [email protected]> wrote: > But I still think that forever forcing Erlang to need an infinite look ahead > custom syntax aware scanner still is a strong argument against the suggested > improvement. > The language designers used certain symbols multiple times in the grammar which could create ambiguous scanning results. The compiler needs to properly handle them, even if it means sacrificing the scanner's simplicity. The C++ camp recently fixed a similar wart with nested templates. You used to place a whitespace between the closing '>'s so the compiler didn't confuse the closing of both template specifications with a shift operator (>>). It now Does The Right Thing even though it was a special case. -- Rich _______________________________________________ erlang-patches mailing list [email protected] http://erlang.org/mailman/listinfo/erlang-patches