PR was merged, tests needed.
On 2017-10-06 19:40:44, alex.jakime...@gmail.com wrote: > See this pull request: https://github.com/rakudo/rakudo/pull/1183 > > Unfortunately not all of the things are covered. For example: > > perl6 -e 'my $x = q:to/foo/; > blah > ' > ===SORRY!=== Error while compiling -e > Ending delimiter foo not found > at -e:3 > ------> <BOL>⏏<EOL> > expecting any of: > whitespace > > Then there's also: > * > https://github.com/rakudo/rakudo/blob/f62ae60c48d1372df18b49aca44e10af44ead2d6/src/Perl6 > /Grammar.nqp#L3741 > * > https://github.com/rakudo/rakudo/blob/f62ae60c48d1372df18b49aca44e10af44ead2d6/src/Perl6/Grammar.nqp#L3780- > L3792 > * > https://github.com/rakudo/rakudo/blob/f62ae60c48d1372df18b49aca44e10af44ead2d6/src/Perl6/Grammar.nqp#L3820- > L3826 > > And maybe other things too. For example, nqp itself prints a similar > error > message and does not mention the starter. I don't know if any user > will ever > see the error message from NQP though. > > So there's a lot to be done to resolve this ticket fully… > > Oh, also! I did not remove “expecting any of:” part. This has to be > done also. > > On 2015-07-18 12:38:41, alex.jakime...@gmail.com wrote: > > Similar issue: https://rt.perl.org/Public/Bug/Display.html?id=125247 > > (unclosed multiline comments). This time it is about other unclosed > > things. > > > > Code: > > say $<word; > > # some code here > > > > Error: > > Unable to parse quote-words subscript; couldn't find right angle > > quote > > at ./test.pl:25 > > ------> <BOL>⏏<EOL> > > expecting any of: > > argument list > > term > > > > Similar problem with: > > say <word; > > say <<word; > > say (word; > > say [word; > > ... more? > > > > 1) "expecting any of" section does not help that much. There is no > > need to > > add terms or argument lists to the end of your file to fix the > > problem, the > > only thing that is actually expected is a closing bracket. > > 2) The end of file does not count as a helpful line number, > > especially if > > the file is long. It would be great to have the same "(corresponding > > < was > > at line 1)"-like message as with multiline comments
