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 does not print error message about stub code #1845

Closed
p6rt opened this issue Jun 17, 2010 · 7 comments
Closed

Rakudo does not print error message about stub code #1845

p6rt opened this issue Jun 17, 2010 · 7 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Jun 17, 2010

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

Searchable as RT75828$

@p6rt
Copy link
Author

p6rt commented Jun 17, 2010

From q@cono.org.ua

15​:37 <@​jnthn> rakudo​: ("62.76.96.200", "62.76.96.201", "62.76.96.202"
... "62.76.96.223").perl.say
15​:37 <+p6eval> rakudo cb0e95​: OUTPUT«("62.76.96.200", "62.76.96.201",
"62.76.96.202")␤»
15​:37 <@​jnthn> rakudo​: ("62.76.96.200", "62.76.96.201",
"62.76.96.202", ... "62.76.96.223").perl.say
15​:37 <+p6eval> rakudo cb0e95​: ( no output )
15​:37 <@​jnthn> Hm
15​:37 <@​moritz_> bug
15​:37 <@​jnthn> Yeah
15​:37 < snarkyboojum> :)
15​:37 <@​moritz_> somwhere the fail() is lost
15​:37 <@​jnthn> It should whine about stub code being executed.
15​:38 <@​jnthn> We fail to fail.
15​:38 <@​jnthn> And thus we fail.

perl6 -e '("62.76.96.200", "62.76.96.201", "62.76.96.202", ...
"62.76.96.223").perl.say'
produce no output

But in REPL it print about stub code executing and hang up

git rev-parse HEAD
17e43e86eedaa241a9f282372aa6db476216df5f

--
Varyanick I. Alex
icq​: 102 575 440
skype​: cono..
q@​cono.org.ua

@p6rt
Copy link
Author

p6rt commented Jul 28, 2010

From @coke

On Thu Jun 17 05​:47​:40 2010, q@​cono.org.ua wrote​:

15​:37 <@​jnthn> rakudo​: ("62.76.96.200", "62.76.96.201", "62.76.96.202"
... "62.76.96.223").perl.say
15​:37 <+p6eval> rakudo cb0e95​: OUTPUT«("62.76.96.200", "62.76.96.201",
"62.76.96.202")␤»
15​:37 <@​jnthn> rakudo​: ("62.76.96.200", "62.76.96.201",
"62.76.96.202", ... "62.76.96.223").perl.say
15​:37 <+p6eval> rakudo cb0e95​: ( no output )
15​:37 <@​jnthn> Hm
15​:37 <@​moritz_> bug
15​:37 <@​jnthn> Yeah
15​:37 < snarkyboojum> :)
15​:37 <@​moritz_> somwhere the fail() is lost
15​:37 <@​jnthn> It should whine about stub code being executed.
15​:38 <@​jnthn> We fail to fail.
15​:38 <@​jnthn> And thus we fail.

perl6 -e '("62.76.96.200", "62.76.96.201", "62.76.96.202", ...
"62.76.96.223").perl.say'
produce no output

But in REPL it print about stub code executing and hang up

git rev-parse HEAD
17e43e86eedaa241a9f282372aa6db476216df5f

This now fails with​:

$ ./perl6 -e '("62.76.96.200", "62.76.96.201", "62.76.96.202", ...
"62.76.96.223").perl.say'
===SORRY!===
Comma found before apparent series operator; please remove comma (or put
parens
  around the ... listop, or use 'fail' instead of ...) at line 1, near
" ... \"62.7"

which is what STD does.

Assigning to moritz for tests.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Jul 28, 2010

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

@p6rt
Copy link
Author

p6rt commented Jul 28, 2010

From @coke

On Thu Jun 17 05​:47​:40 2010, q@​cono.org.ua wrote​:

15​:37 <@​jnthn> rakudo​: ("62.76.96.200", "62.76.96.201", "62.76.96.202"
... "62.76.96.223").perl.say
15​:37 <+p6eval> rakudo cb0e95​: OUTPUT«("62.76.96.200", "62.76.96.201",
"62.76.96.202")␤»
15​:37 <@​jnthn> rakudo​: ("62.76.96.200", "62.76.96.201",
"62.76.96.202", ... "62.76.96.223").perl.say
15​:37 <+p6eval> rakudo cb0e95​: ( no output )
15​:37 <@​jnthn> Hm
15​:37 <@​moritz_> bug
15​:37 <@​jnthn> Yeah
15​:37 < snarkyboojum> :)
15​:37 <@​moritz_> somwhere the fail() is lost
15​:37 <@​jnthn> It should whine about stub code being executed.
15​:38 <@​jnthn> We fail to fail.
15​:38 <@​jnthn> And thus we fail.

perl6 -e '("62.76.96.200", "62.76.96.201", "62.76.96.202", ...
"62.76.96.223").perl.say'
produce no output

But in REPL it print about stub code executing and hang up

git rev-parse HEAD
17e43e86eedaa241a9f282372aa6db476216df5f

This now fails with​:

$ ./perl6 -e '("62.76.96.200", "62.76.96.201", "62.76.96.202", ...
"62.76.96.223").perl.say'
===SORRY!===
Comma found before apparent series operator; please remove comma (or put
parens
  around the ... listop, or use 'fail' instead of ...) at line 1, near
" ... \"62.7"

which is what STD does.

Assigning to moritz for tests.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Aug 24, 2010

From @moritz

The series-after-comma is now tested in t/spec/S03-operators/series.t.
Stub code execution is now tested in t/spec/S12-class/stubs.t (though
will probably be moved to a more appropriate file).

Cheers,
Moritz

@p6rt
Copy link
Author

p6rt commented Aug 24, 2010

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

@p6rt p6rt closed this as completed Aug 24, 2010
@p6rt
Copy link
Author

p6rt commented Aug 24, 2010

From @kyleha

This is an automatically generated mail to inform you that tests are now available in t/spec/S03-operators/series.t

commit 095f18e9b4d06aaf9c797bbbb100a5f07838928d
Author​: moritz <moritz@​c213334d-75ef-0310-aa23-eaa082d1ae64>
Date​: Tue Aug 24 09​:24​:24 2010 +0000

  [t/spec] test for RT #​75828, series operator after comma is caught
 
  git-svn-id​: http://svn.pugscode.org/pugs@&#8203;32097 c213334d-75ef-0310-aa23-eaa082d1ae64

Inline Patch
diff --git a/t/spec/S03-operators/series.t b/t/spec/S03-operators/series.t
index d923c1c..9119214 100644
--- a/t/spec/S03-operators/series.t
+++ b/t/spec/S03-operators/series.t
@@ -3,7 +3,7 @@ use Test;
 
 # L<S03/List infix precedence/"the series operator">
 
-plan 121;
+plan 122;
 
 # single-term series
 
@@ -225,6 +225,9 @@ is (1, +* ... *).[^5].join('|'), (1 xx 5).join('|'),
 # RT #75768
 is ~(1...10)[2...4], '3 4 5', 'can index series with series';
 
+# RT #75828
+eval_dies_ok '1, 2, 3, ... 5', 'comma before series operator is caught';
+
 done_testing;
 
 # vim: ft=perl6

@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