You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Result:
===SORRY!=== Error while compiling ./test.pl
Confused
at ./test.pl:2
------> say 0b000⏏l01;
The error message could be better. For example:
Code:
say :2<000l01>;
Result:
===SORRY!===
Invalid character 'L' in number literal
It would be great (if it is easy to implement) if it also mentioned that it
is a hex/binary/octal number (not just a number literal), because some
people might be unaware of that notation (kid-friendly error messages?).
This made the error message as awesome as it was suggested in the OP. Problem is, some spectests were failing. Things like :42foo started to complain needlessly. I guess it's still possible to resolve this ticket, I was simply doing it wrong.
On 2015-07-24 15:53:57, alex.jakimenko@gmail.com wrote:
Code:
say 0b000l01;
Result:
===SORRY!=== Error while compiling ./test.pl
Confused
at ./test.pl:2
------> say 0b000⏏l01;
The error message could be better. For example:
Code:
say :2<000l01>;
Result:
===SORRY!===
Invalid character 'L' in number literal
It would be great (if it is easy to implement) if it also mentioned that it
is a hex/binary/octal number (not just a number literal), because some
people might be unaware of that notation (kid-friendly error messages?).
Migrated from rt.perl.org#125684 (status was 'new')
Searchable as RT125684$
The text was updated successfully, but these errors were encountered: