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

\b should be quoted in error messages #4296

Closed
p6rt opened this issue Jun 5, 2015 · 4 comments
Closed

\b should be quoted in error messages #4296

p6rt opened this issue Jun 5, 2015 · 4 comments

Comments

@p6rt
Copy link

p6rt commented Jun 5, 2015

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

Searchable as RT125335$

@p6rt
Copy link
Author

p6rt commented Jun 5, 2015

From @AlexDaniel

Code​:
say +("\b" x 70);

Result (in my terminal)​:
Cannot convert stri' (indicated by ⏏)-10 number must begin with valid
digits or '.' in '⏏
  in block <unit> at ./test.pl​:2

As you can see, the output is broken because of \b. This behavior probably
depends on the terminal (in emacs, for example, I see ^H), but I think that
printing \b without escaping it first is a bad idea (at least in error
messages).

@p6rt
Copy link
Author

p6rt commented Jun 29, 2015

From @jnthn

On Fri Jun 05 08​:00​:18 2015, alex.jakimenko@​gmail.com wrote​:

Code​:
say +("\b" x 70);

Result (in my terminal)​:
Cannot convert stri' (indicated by ⏏)-10 number must begin with valid
digits or '.' in '⏏
in block <unit> at ./test.pl​:2

As you can see, the output is broken because of \b. This behavior probably
depends on the terminal (in emacs, for example, I see ^H), but I think that
printing \b without escaping it first is a bad idea (at least in error
messages).

Most amusing bug I've fixed all day. Added test coverage in S32-exceptions/misc.t.

@p6rt
Copy link
Author

p6rt commented Jun 29, 2015

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

@p6rt p6rt closed this as completed Jun 29, 2015
@p6rt
Copy link
Author

p6rt commented Jun 29, 2015

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant