New issue
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
chr(999999999999999999999999999) – chr codepoint cannot be negative #4477
Comments
From @AlexDanielCode: Result: Well, it is not negative. |
From @cokeOn Fri Aug 14 21:13:01 2015, alex.jakimenko@gmail.com wrote:
Behavior has changed to the more accurate: 13:17 < [Coke]> m: say chr 999999999999999999999999999 I think this is closable with tests. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielThis is not closable at all. Now it segfaults. Code: Result: Code: Result: Code: Result: |
From @AlexDanielLots of poking around: http://irclog.perlgeek.de/perl6/2016-01-28#i_11951375 |
From @zoffixznetA lot of the aforementioned issues no longer occur, however, I'm still spotting these two: 15:26 BrokenRobot m: say chr 2**63 |
From zefram@fysh.org
It's right that this signal an error, but the error message in incorrect. -zefram |
From @lizmatFixed with rakudo/rakudo@20fa14be7a , tests needed.
|
From @zoffixznetTests in: |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125817 (status was 'resolved')
Searchable as RT125817$
The text was updated successfully, but these errors were encountered: