[perl #130261] [LTA] Error message for unclosed curly quote points to the last line of the file <[email protected]>

[email protected] ("Aleks-Daniel Jakimenko-Aleksejev via RT")
Newsgroups perl.perl6.compiler
Message-ID <[email protected]>
Tests in
https://github.com/perl6/roast/commit/ceabda6337364b5f1cec3c1c5bcb89787f9bcedf

On 2018-01-08 15:18:46, [email protected] wrote:
> Note that the error message is still LTA (says “corresponding starter”
> instead
> of mentioning “’”), for further progress see RT#125641.
>
> On 2018-01-08 15:16:47, [email protected] wrote:
> > Ah. This was fixed. Here's the pull request:
> > https://github.com/rakudo/rakudo/pull/1183
> > And here's the right commit:
> >
>
https://github.com/rakudo/rakudo/pull/1183/commits/6542bb8032e7203b8736655075dbd3452856bc93
> >
> > There should be tests for this already, I think.
> >
> > On 2016-12-04 10:22:37, [email protected] wrote:
> > > Code:
> > > say ‘hello';
> > > say 42;
> > > say 50;
> > >
> > > Result:
> > > == =SORRY!=== Error while compiling -e
> > > Unable to parse expression in smart single quotes; couldn't find
> > > final
> > > "’"
> > > at -e:3
> > > ------> say 50;⏏<EOL>
> > > expecting any of:
> > > argument list
> > > smart single quotes
> > > term
> > >
> > > While the error message is right, it would be better if it also
> > > printed some information on where the initial curly quote is. As an
> > > example, see what happens if you try to do the same thing with a
> > > multiline comment (RT #125247):
> > >
> > > Code:
> > > say #`‘hello';
> > > say 42;
> > > say 50;
> > >
> > > Result:
> > > == =SORRY!=== Error while compiling -e
> > > Couldn't find terminator ’ (corresponding ‘ was at line 1)
> > > at -e:3
> > > ------> say 50;⏏<EOL>
> > > expecting any of:
> > > ’
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.