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 allows using '#`' (embedded comment) without following opening bracket, should not #3960

Open
p6rt opened this issue May 3, 2015 · 4 comments
Labels

Comments

@p6rt
Copy link

@p6rt p6rt commented May 3, 2015

Migrated from rt.perl.org#124679 (status was 'open')

Searchable as RT124679$

@p6rt
Copy link
Author

@p6rt p6rt commented Jul 1, 2015

@usev6 - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

@p6rt p6rt commented Jul 1, 2015

From @usev6

This ticket is about a failing test (fudged 'todo') in S32-exceptions/misc.t. Rakudo does not complain about a plain '#`', whereas STD does​:

$ perl6 -e '#`'
$ viv -e '#`'
===SORRY!===
Opening bracket is required for #` comment at (eval) line 1​:
------> #`<EOL>
Parse failed

According to S02 '#`' has to be followed by an opening bracket character​: http://design.perl6.org/S02.html#Embedded_Comments

@p6rt
Copy link
Author

@p6rt p6rt commented Dec 2, 2017

From @AlexDaniel

But why? “#` foo” looks like a fine normal comment, why should it error out on a perfectly normal behavior?

I think this ticket is rejectable. Someone with bigger whatever should reject it.

On 2015-07-01 12​:54​:40, bartolin@​gmx.de wrote​:

This ticket is about a failing test (fudged 'todo') in S32-
exceptions/misc.t. Rakudo does not complain about a plain '#`',
whereas STD does​:

$ perl6 -e '#`'
$ viv -e '#`'
===SORRY!===
Opening bracket is required for #` comment at (eval) line 1​:
------> #`<EOL>
Parse failed

According to S02 '#`' has to be followed by an opening bracket
character​: http://design.perl6.org/S02.html#Embedded_Comments

@p6rt
Copy link
Author

@p6rt p6rt commented Jan 6, 2018

From @AlexDaniel

Ah. Now I see why.

Consider this​:

#`| foo |

↑ that does not DWIM. And it's right to assume that you can do it because s||| works just fine. So either it should understand stuff like this, or it can give an error message as todo-ed.

So no, this is not rejectable. And the actual issue is about non-bracket characters, I think.

On 2017-12-02 05​:42​:13, alex.jakimenko@​gmail.com wrote​:

But why? “#` foo” looks like a fine normal comment, why should it
error out on
a perfectly normal behavior?

I think this ticket is rejectable. Someone with bigger whatever should
reject
it.

On 2015-07-01 12​:54​:40, bartolin@​gmx.de wrote​:

This ticket is about a failing test (fudged 'todo') in S32-
exceptions/misc.t. Rakudo does not complain about a plain '#`',
whereas STD does​:

$ perl6 -e '#`'
$ viv -e '#`'
===SORRY!===
Opening bracket is required for #` comment at (eval) line 1​:
------> #`<EOL>
Parse failed

According to S02 '#`' has to be followed by an opening bracket
character​: http://design.perl6.org/S02.html#Embedded_Comments

@p6rt p6rt added the at_larry label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.