We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrated from rt.perl.org#127857 (status was 'new')
Searchable as RT127857$
The text was updated successfully, but these errors were encountered:
Code: loop (my $x = 0, $x < 10, $x++) {}
Result: ===SORRY!=== Error while compiling -e Malformed loop spec at -e:1 ------> loop (my $x = 0, $x < 10, $x++�) {}
The error message is not bad at all. But it would be awesome if it could detect that the programmer used commas instead of semicolons.
Sorry, something went wrong.
There is a PR but it's really bad: rakudo/rakudo#1188
On 2016-04-07 17:05:15, alex.jakimenko@gmail.com wrote:
Code: loop (my $x = 0, $x < 10, $x++) {} Result: ===SORRY!=== Error while compiling -e Malformed loop spec at -e:1 ------> loop (my $x = 0, $x < 10, $x++�) {} The error message is not bad at all. But it would be awesome if it could detect that the programmer used commas instead of semicolons.
On a slightly more positive note, that PR indeed resolves this ticket. I think the new error message is clear enough.
On 2017-10-08 00:52:36, alex.jakimenko@gmail.com wrote:
There is a PR but it's really bad: rakudo/rakudo#1188 On 2016-04-07 17:05:15, alex.jakimenko@gmail.com wrote: Code: loop (my $x = 0, $x < 10, $x++) {} Result: ===SORRY!=== Error while compiling -e Malformed loop spec at -e:1 ------> loop (my $x = 0, $x < 10, $x++�) {} The error message is not bad at all. But it would be awesome if it could detect that the programmer used commas instead of semicolons.
Closing as rakudo/rakudo#1188 was merged.
No branches or pull requests
Migrated from rt.perl.org#127857 (status was 'new')
Searchable as RT127857$
The text was updated successfully, but these errors were encountered: