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

Defining a postcircumfix:<{ }> method causes unnecessary confusion in Rakudo #1326

Closed
p6rt opened this issue Sep 28, 2009 · 5 comments
Closed
Labels

Comments

@p6rt
Copy link

p6rt commented Sep 28, 2009

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

Searchable as RT69438$

@p6rt
Copy link
Author

p6rt commented Sep 28, 2009

From @masak

This be Rakudo 0331d6 inside Parrot r41527.

$ cat file-exhibiting-the-problem
class A {
  method postcircumfix​:<{ }>($table) {
  }
}

{
  1;
}

$ perl6 file-exhibiting-the-problem
Confused at line 6, near "{\n 1;\n}"
[...]

Adding a semicolon between the two outermost blocks in the file makes
the confusion go away. The point of this ticket, however, is that this
shouldn't be necessary, since line-ending closing curlies have
implicit semicolons.

@p6rt
Copy link
Author

p6rt commented Apr 19, 2010

From @jnthn

On Mon Sep 28 03​:09​:50 2009, masak wrote​:

This be Rakudo 0331d6 inside Parrot r41527.

$ cat file-exhibiting-the-problem
class A {
method postcircumfix​:<{ }>($table) {
}
}

{
1;
}

$ perl6 file-exhibiting-the-problem
Confused at line 6, near "{\n 1;\n}"
[...]

Adding a semicolon between the two outermost blocks in the file makes
the confusion go away. The point of this ticket, however, is that this
shouldn't be necessary, since line-ending closing curlies have
implicit semicolons.

Seems to be fine in latest Rakudo; given to moritz++ for spectests.

Thanks,

Jonathan

@p6rt
Copy link
Author

p6rt commented Apr 19, 2010

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

@p6rt
Copy link
Author

p6rt commented Apr 20, 2010

From @moritz

Tested in t/spec/S06-operator-overloading/methods.t.

@p6rt
Copy link
Author

p6rt commented Apr 20, 2010

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

@p6rt p6rt closed this as completed Apr 20, 2010
@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