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
"maximum recursion depth exceeded" after making a Malformed routine definition #1240
Comments
From @carbin
Confirmed by: <jnthn> Can reproduce it here too. -- |
From @bbkrOn Kiev build $ perl6
But such declaration should fail according to STD: [18:01] <p6eval> std 31642: so leaving unchanged |
The RT System itself - Status changed from 'new' to 'open' |
From @carbinOn Mon Jul 12 09:02:28 2010, bbkr wrote:
Indeed it should, hence my comment "# wrong ofc". The bug is that attempting to call a misdecleared subroutine should not If running "sub foo;" and then calling "foo;" on the REPL no longer -- |
From @jnthnOn Mon Jul 12 09:23:58 2010, carlin wrote:
Just checked latest Rakudo and...
So, better. /jnthn |
From @moritzNow tested in S32-exceptions/misc.t |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#68710 (status was 'resolved')
Searchable as RT68710$
The text was updated successfully, but these errors were encountered: