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

Rakudo only passes t/spec/S19-command-line/dash-e.t with a UTF-8 locale #3047

Closed
p6rt opened this issue Feb 10, 2013 · 4 comments
Closed

Rakudo only passes t/spec/S19-command-line/dash-e.t with a UTF-8 locale #3047

p6rt opened this issue Feb 10, 2013 · 4 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Feb 10, 2013

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

Searchable as RT116709$

@p6rt
Copy link
Author

p6rt commented Feb 10, 2013

From @nwc10

Compare​:

$ LC_ALL=en_US.utf8 ./perl6 -Ilib t/spec/S19-command-line/dash-e.t
1..3
ok 1 - -e print $something works
ok 2 - -e print $something works with non-ASCII string literals
ok 3 - -e works with non-ASCII program texts

$ LC_ALL=C ./perl6 -Ilib t/spec/S19-command-line/dash-e.t
1..3
ok 1 - -e print $something works
not ok 2 - -e print $something works with non-ASCII string literals
# got out​: "ȧ"
# expected out​: "ȧ"
not ok 3 - -e works with non-ASCII program texts
# got status​: 1
# got out​: ""
# expected out​: "23"
# got err​: "\x[1b][31m===\x[1b][0mSORRY!\x[1b][31m===\x[1b][0m\nTwo terms in a row\nat -e​:1\n------> \x[1b][32mprint <1 2> \x[1b][33m⏏\x[1b][31m»+« <1 1>\x[1b][0m\n expecting any of​:\n postfix\n infix or meta-infix\n infix stopper\n statement end\n statement modifier\n statement modifier loop\n"
# expected err​: ""
# Looks like you failed 2 tests of 3

My opinion is that the spectest shouldn't *fail* if the locale isn't UTF-8.
Should it be skipping?

(Also, should stderr have all the ANSI escape codes if it's not a tty?
I think that clang changes its behaviour if you capture stderr.)

Nicholas Clark

@p6rt
Copy link
Author

p6rt commented May 8, 2018

From @skids

Well, the current test file succeeds in both cases. This ticket is so old
it may more be the tests have changed than anything else, but there was
also lot of charset work so maybe it is actually fixed.

If you can still figure out how to break something with LC_ALL,
please re-file a github issue at https://github.com/rakudo/rakudo/issues

$ LC_ALL=en_US.utf8 perl6 S19-command-line/dash-e.t
1..4
ok 1 - -e print $something works
ok 2 - -e print $something works with non-ASCII string literals
ok 3 - -e works with non-ASCII program texts
ok 4 - -e works correctly as a stopper
$ LC_ALL=C perl6 S19-command-line/dash-e.t
1..4
ok 1 - -e print $something works
ok 2 - -e print $something works with non-ASCII string literals
ok 3 - -e works with non-ASCII program texts
ok 4 - -e works correctly as a stopper

@p6rt
Copy link
Author

p6rt commented May 8, 2018

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

@p6rt p6rt closed this as completed May 8, 2018
@p6rt
Copy link
Author

p6rt commented May 8, 2018

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

@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