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

Still problems with syntactic errors in the REPL #5641

Closed
p6rt opened this issue Sep 4, 2016 · 4 comments
Closed

Still problems with syntactic errors in the REPL #5641

p6rt opened this issue Sep 4, 2016 · 4 comments

Comments

@p6rt
Copy link

p6rt commented Sep 4, 2016

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

Searchable as RT129198$

@p6rt
Copy link
Author

p6rt commented Sep 4, 2016

From public@leidisch.net

Hello!

This is related to bug #​129179. (My reply to perl6-followup@​perl.org
didn't seem to get through. I couldn't comment via the web interface
as a guest and couldn't open the bug after setting up an RT account
either, so I'll just open a new ticket. Feel free to merge.)

Thanks for the quick fix for #​129179, but I think there are still problems​:

$ uname -a
Linux asus 4.4.0-36-generic #​55-Ubuntu SMP Thu Aug 11 18​:01​:55 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
$ perl6 -v
This is Rakudo version 2016.08.1-102-ge39ab83 built on MoarVM version
2016.08-32-ge52414d
implementing Perl 6.c.
$ perl6
You may want to `panda install Readline` or `panda install Linenoise`
or use rlwrap for a line editor

To exit type 'exit' or '^D'

sub }
===SORRY!=== Error while compiling​:
Missing block
------> sub ⏏}
  expecting any of​:
  new name to be defined
1+1
===SORRY!=== Error while compiling​:
Missing block
------> sub ⏏}
  expecting any of​:
  new name to be defined

Regards,

Daniel

@p6rt
Copy link
Author

p6rt commented Sep 5, 2016

From @zoffixznet

Thanks for the report.

The issue has now been fixed in rakudo/rakudo@77d9d41fc4

(Tests added in the same commit).

@p6rt
Copy link
Author

p6rt commented Sep 5, 2016

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

@p6rt
Copy link
Author

p6rt commented Sep 5, 2016

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

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