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

Paired delimiters with Linear B syllables #15476

Closed
p5pRT opened this issue Jul 26, 2016 · 6 comments
Closed

Paired delimiters with Linear B syllables #15476

p5pRT opened this issue Jul 26, 2016 · 6 comments

Comments

@p5pRT
Copy link

p5pRT commented Jul 26, 2016

Migrated from rt.perl.org#128737 (status was 'rejected')

Searchable as RT128737$

@p5pRT
Copy link
Author

p5pRT commented Jul 26, 2016

From @cpansprout

$ perl -e 'eval "print q\x{U+10028}Hello, whirled!\n\x{U+10029}" or die;'
Hello, whirled!

Wow.

U+28 is ‘(’ and U+29 is ‘)’. We have a 32-bit wrapping problem.

Same results in 5.8.7 and 5.25.3.

--

Father Chrysostomos

@p5pRT
Copy link
Author

p5pRT commented Jul 26, 2016

From @cpansprout

On Tue Jul 26 00​:12​:42 2016, sprout wrote​:

$ perl -e 'eval "print q\x{U+10028}Hello, whirled!\n\x{U+10029}" or die;'
Hello, whirled!

Wow.

U+28 is ‘(’ and U+29 is ‘)’. We have a 32-bit wrapping problem.

Scratch that. I misread the code, and then I put typoes in my test. This report is bogus. (Though I still think there is an I32 bug, but I’ll open another ticket if I find it.)

--

Father Chrysostomos

@p5pRT
Copy link
Author

p5pRT commented Jul 26, 2016

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

@p5pRT
Copy link
Author

p5pRT commented Jul 26, 2016

@cpansprout - Status changed from 'open' to 'rejected'

@p5pRT p5pRT closed this as completed Jul 26, 2016
@p5pRT
Copy link
Author

p5pRT commented Jul 26, 2016

From zefram@fysh.org

Father Chrysostomos wrote​:

U+28 is "(" and U+29 is ")". We have a 32-bit wrapping problem.

That would be a 16-bit wrapping problem, but it's not. "\x{U+10028}" eq
"\0". The problem we have is \x{} accepting arbitrary non-numeric crap
that it won't interpret. (It does give a warning, if one turns them on.)
Since it's ignoring the "U" and everything following, it seems to me that
this is not a meaningful construct and should not be accepted at all.
"\x{}" with nothing in the braces is accepted (without even a warning)
and gives a very different silly result; that should be illegal too.

-zefram

@p5pRT
Copy link
Author

p5pRT commented Jul 26, 2016

From @cpansprout

On Tue Jul 26 01​:22​:33 2016, zefram@​fysh.org wrote​:

Father Chrysostomos wrote​:

U+28 is "(" and U+29 is ")". We have a 32-bit wrapping problem.

That would be a 16-bit wrapping problem, but it's not. "\x{U+10028}" eq
"\0".

I know. I wasn’t thinking. (Just now I typed ‘use Devel​::Peek’ in toke.c! I must be tired.)

  The problem we have is \x{} accepting arbitrary non-numeric crap

that it won't interpret. (It does give a warning, if one turns them on.)
Since it's ignoring the "U" and everything following, it seems to me that
this is not a meaningful construct and should not be accepted at all.
"\x{}" with nothing in the braces is accepted (without even a warning)
and gives a very different silly result; that should be illegal too.

I’m not interested in disturbing that hornet’s nest right now.

--

Father Chrysostomos

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

No branches or pull requests

1 participant