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

{redo} prints a newline to STDERR #1483

Closed
p6rt opened this issue Feb 2, 2010 · 7 comments
Closed

{redo} prints a newline to STDERR #1483

p6rt opened this issue Feb 2, 2010 · 7 comments

Comments

@p6rt
Copy link

p6rt commented Feb 2, 2010

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

Searchable as RT72442$

@p6rt
Copy link
Author

p6rt commented Feb 2, 2010

From @moritz

$ perl6 -e '{redo}'|wc -l

0
$

Rakudo prints a newline to STDERR, nothing else. That's a bit
less-than-awesome, I'd expect a warning like "redo without a block at
..." or so.

Cheers,
Moritz

@p6rt
Copy link
Author

p6rt commented Aug 12, 2010

From @coke

On Tue Feb 02 00​:32​:30 2010, moritz wrote​:

$ perl6 -e '{redo}'|wc -l

0
$

Rakudo prints a newline to STDERR, nothing else. That's a bit
less-than-awesome, I'd expect a warning like "redo without a block at
..." or so.

Cheers,
Moritz

Now with even less awesome​:

$ ./perl6 -e '{redo}'
at line 1
Null PMC access in setprop()
  in main program body at line 1

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Aug 12, 2010

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

@p6rt
Copy link
Author

p6rt commented Oct 22, 2011

From @coke

On Wed Aug 11 19​:12​:51 2010, coke wrote​:

On Tue Feb 02 00​:32​:30 2010, moritz wrote​:

$ perl6 -e '{redo}'|wc -l

0
$

Rakudo prints a newline to STDERR, nothing else. That's a bit
less-than-awesome, I'd expect a warning like "redo without a block
at
..." or so.

Cheers,
Moritz

Now with even less awesome​:

$ ./perl6 -e '{redo}'
at line 1
Null PMC access in setprop()
in main program body at line 1

How now?

$ ./perl6 -e '{redo}'
Warning
$

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Apr 5, 2012

From @jnthn

On Fri Oct 21 18​:24​:33 2011, coke wrote​:

On Wed Aug 11 19​:12​:51 2010, coke wrote​:

On Tue Feb 02 00​:32​:30 2010, moritz wrote​:

$ perl6 -e '{redo}'|wc -l

0
$

Rakudo prints a newline to STDERR, nothing else. That's a bit
less-than-awesome, I'd expect a warning like "redo without a block
at
..." or so.

Cheers,
Moritz

Now with even less awesome​:

$ ./perl6 -e '{redo}'
at line 1
Null PMC access in setprop()
in main program body at line 1

How now?

$ ./perl6 -e '{redo}'
Warning
$

Now it's​:

C​:\consulting\rakudo>perl6 -e "{redo}"
redo without loop construct

Which is much nicer. Tagging testneeded.

/jnthn

@p6rt
Copy link
Author

p6rt commented Jun 2, 2012

From @diakopter

On Thu Apr 05 07​:13​:29 2012, jnthn@​jnthn.net wrote​:

On Fri Oct 21 18​:24​:33 2011, coke wrote​:

On Wed Aug 11 19​:12​:51 2010, coke wrote​:

On Tue Feb 02 00​:32​:30 2010, moritz wrote​:

$ perl6 -e '{redo}'|wc -l

0
$

Rakudo prints a newline to STDERR, nothing else. That's a bit
less-than-awesome, I'd expect a warning like "redo without a
block
at
..." or so.

Cheers,
Moritz

Now with even less awesome​:

$ ./perl6 -e '{redo}'
at line 1
Null PMC access in setprop()
in main program body at line 1

How now?

$ ./perl6 -e '{redo}'
Warning
$

Now it's​:

C​:\consulting\rakudo>perl6 -e "{redo}"
redo without loop construct

Which is much nicer. Tagging testneeded.

/jnthn

19​:46 <+dalek> roast​: 6a6a83f | diakopter++ | S04-statements/redo.t​:
19​:46 <+dalek> roast​: test RT #​72442. resolves ticket.
19​:46 <+dalek> roast​: review​:
Raku/roast@6a6a83f0a6

@p6rt
Copy link
Author

p6rt commented Jun 2, 2012

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

@p6rt p6rt closed this as completed Jun 2, 2012
@p6rt p6rt added the testneeded 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
Development

No branches or pull requests

1 participant