Skip to content
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

LTA error message when too high a digit occurs in base conversion in Rakudo #2131

Closed
p6rt opened this issue Sep 1, 2010 · 5 comments
Closed
Labels

Comments

@p6rt
Copy link

p6rt commented Sep 1, 2010

Migrated from rt.perl.org#77626 (status was 'resolved')

Searchable as RT77626$

@p6rt
Copy link
Author

p6rt commented Sep 1, 2010

From @masak

<ash_> rakudo​: say :10(​:16<10>)
<p6eval> rakudo dc9900​: OUTPUT«16␤»
<ash_> rakudo​: say :2(​:16<10>)
<p6eval> rakudo dc9900​: OUTPUT«DON'T PANIC! Invalid character (6)!
Please try again :) [...]
<masak> could probably do better than that error message.
<pmichaud> agreed.
<TimToady> stringifying without evaluating?
<pmichaud> with evaluating, in this case
<TimToady> oh, yes
<TimToady> with
<pmichaud> since :16<10> is '16'
<TimToady> 16 has a 6, duh

My preferred error message would be something on the order of "The
number contains a 6 but you're interpreting it as a base-2 number."

@p6rt
Copy link
Author

p6rt commented Sep 1, 2010

From @pmichaud

On Wed, Sep 01, 2010 at 10​:19​:21AM -0700, Carl Mäsak wrote​:

<ash_> rakudo​: say :2(​:16<10>)
<p6eval> rakudo dc9900​: OUTPUT«DON'T PANIC! Invalid character (6)!

My preferred error message would be something on the order of "The
number contains a 6 but you're interpreting it as a base-2 number."

Not only that, but it should fail and not die.

Pm

@p6rt
Copy link
Author

p6rt commented Sep 1, 2010

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented May 29, 2012

From @moritz

It now complains correctly that the argument to :10() is a number and
not a string.

@p6rt
Copy link
Author

p6rt commented May 29, 2012

@moritz - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed May 29, 2012
@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant