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

my @a = (1,2,3,4); @a.>>.say doesn't work #1743

Closed
p6rt opened this issue May 4, 2010 · 10 comments
Closed

my @a = (1,2,3,4); @a.>>.say doesn't work #1743

p6rt opened this issue May 4, 2010 · 10 comments
Labels

Comments

@p6rt
Copy link

p6rt commented May 4, 2010

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

Searchable as RT74890$

@p6rt
Copy link
Author

p6rt commented May 4, 2010

From @zhuomingliang

09​:44 JimmyZ rakudo​: my @​a = (1,2,3,4); @​a>>.say
09​:44 p6eval rakudo 1eef08​: OUTPUT«1â�¤2â�¤3â�¤4â�¤Â»
09​:44 JimmyZ rakudo​: my @​a = (1,2,3,4); @​a.>>.say
09​:44 p6eval rakudo 1eef08​: OUTPUT«Confused at line 11, near "@​a.>>.say"â�¤current instr.​: 'perl6;HLL;Grammar;panic' pc 501 (ext/nqp-rx/src/stage0/HLL-s0.pir​:327)â�¤Â»

�此�你身��康�天天快�
��亮

 

@p6rt
Copy link
Author

p6rt commented Jun 27, 2010

From @cognominal

say <1 2 3>.>>.perl
Confused at line 1, near "say <1 2 3"
say <1 2 3>.>>perl
Confused at line 1, near "say <1 2 3"
say <1 2 3>>>perl
Confused at line 1, near "say <1 2 3"

--
cognominal stef

@p6rt
Copy link
Author

p6rt commented Jun 28, 2010

From @masak

On Sun Jun 27 14​:21​:29 2010, cognominal wrote​:

say <1 2 3>.>>.perl
Confused at line 1, near "say <1 2 3"
say <1 2 3>.>>perl
Confused at line 1, near "say <1 2 3"
say <1 2 3>>>perl
Confused at line 1, near "say <1 2 3"

Only the first of those three is valid syntax, according to STD​:

$ std -e 'say <1 2 3>.>>.perl'
ok 0​:00.99 2476m

$ std -e 'say <1 2 3>.>>perl'
===SORRY!===
Confused at your script line 1​:
------> say <1 2 3>.>>�perl
  expecting any of​:
  postfix
  postfix_prefix_meta_operator
Parse failed
FAILED 0​:00.89 2477m

$ std -e 'say <1 2 3>>>perl'
===SORRY!===
Preceding context expects a term, but found infix > instead at your script line 1​:
------> say <1 2 3>>�>perl
Parse failed
FAILED 0​:00.89 2477m

@p6rt
Copy link
Author

p6rt commented Jun 28, 2010

From [Unknown Contact. See original ticket]

On Sun Jun 27 14​:21​:29 2010, cognominal wrote​:

say <1 2 3>.>>.perl
Confused at line 1, near "say <1 2 3"
say <1 2 3>.>>perl
Confused at line 1, near "say <1 2 3"
say <1 2 3>>>perl
Confused at line 1, near "say <1 2 3"

Only the first of those three is valid syntax, according to STD​:

$ std -e 'say <1 2 3>.>>.perl'
ok 0​:00.99 2476m

$ std -e 'say <1 2 3>.>>perl'
===SORRY!===
Confused at your script line 1​:
------> say <1 2 3>.>>�perl
  expecting any of​:
  postfix
  postfix_prefix_meta_operator
Parse failed
FAILED 0​:00.89 2477m

$ std -e 'say <1 2 3>>>perl'
===SORRY!===
Preceding context expects a term, but found infix > instead at your script line 1​:
------> say <1 2 3>>�>perl
Parse failed
FAILED 0​:00.89 2477m

@p6rt
Copy link
Author

p6rt commented Jun 28, 2010

@masak - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Aug 18, 2010

@coke - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Oct 10, 2011

From @coke

On Tue May 04 07​:51​:35 2010, jimmy wrote​:

09​:44 JimmyZ rakudo​: my @​a = (1,2,3,4); @​a>>.say
09​:44 p6eval rakudo 1eef08​: OUTPUT«1â�¤2â�¤3â�¤4â�¤Â»
09​:44 JimmyZ rakudo​: my @​a = (1,2,3,4); @​a.>>.say
09​:44 p6eval rakudo 1eef08​: OUTPUT«Confused at line 11, near
"@​a.>>.say"â�¤current instr.​: 'perl6;HLL;Grammar;panic' pc 501
(ext/nqp-
rx/src/stage0/HLL-s0.pir​:327)â�¤Â»

�此�你身��康�天天快�
��亮

Pretty much unchanged with a recent rakudo​:

16​:58 < [Coke]> rakudo​: my @​a = (1,2,3,4); @​a>>.say
16​:58 <+p6eval> rakudo 38907e​: OUTPUT«1â�¤3â�¤2â�¤4â�¤Â»
16​:58 < [Coke]> my @​a = (1,2,3,4); @​a.>>.say
16​:58 < [Coke]> rakudo​: my @​a = (1,2,3,4); @​a.>>.say
16​:58 <+p6eval> rakudo 38907e​: OUTPUT«===SORRY!===â�¤Confused at line 1,
near
  "@​a.>>.say "â�¤Â»

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented May 29, 2012

From @diakopter

On Mon Jun 28 03​:32​:44 2010, masak wrote​:

On Sun Jun 27 14​:21​:29 2010, cognominal wrote​:

say <1 2 3>.>>.perl
Confused at line 1, near "say <1 2 3"
say <1 2 3>.>>perl
Confused at line 1, near "say <1 2 3"
say <1 2 3>>>perl
Confused at line 1, near "say <1 2 3"

Only the first of those three is valid syntax, according to STD​:

$ std -e 'say <1 2 3>.>>.perl'
ok 0​:00.99 2476m

$ std -e 'say <1 2 3>.>>perl'
===SORRY!===
Confused at your script line 1​:
------> say <1 2 3>.>>�perl
expecting any of​:
postfix
postfix_prefix_meta_operator
Parse failed
FAILED 0​:00.89 2477m

$ std -e 'say <1 2 3>>>perl'
===SORRY!===
Preceding context expects a term, but found infix > instead at your
script line 1​:
------> say <1 2 3>>�>perl
Parse failed
FAILED 0​:00.89 2477m

This now seems fixed​: marking testneeded.

14​:46 <diakopter> r​: say <1 2 3>.>>.perl
14​:46 <p6eval> rakudo 223419​: OUTPUT«===SORRY!===â�¤Confusedâ�¤at
/tmp/Dk_T5keW13​:1â�¤Â»
14​:46 <diakopter> r​: say <1 2 3>.>>perl
14​:46 <p6eval> rakudo 223419​: OUTPUT«===SORRY!===â�¤Confusedâ�¤at
/tmp/uwVzeZjmZY​:1â�¤Â»
14​:47 <diakopter> r​: say <1 2 3>>>perl
14​:47 <p6eval> rakudo 223419​: OUTPUT«===SORRY!===â�¤Preceding context
expects a term, but
  found infix > insteadâ�¤at /tmp/RNSRmkCf3R​:1â�¤Â»

@p6rt
Copy link
Author

p6rt commented Nov 14, 2013

From @coke

On Tue May 04 07​:51​:35 2010, jimmy wrote​:

09​:44 JimmyZ rakudo​: my @​a = (1,2,3,4); @​a>>.say
09​:44 p6eval rakudo 1eef08​: OUTPUT«1â�¤2â�¤3â�¤4â�¤Â»
09​:44 JimmyZ rakudo​: my @​a = (1,2,3,4); @​a.>>.say
09​:44 p6eval rakudo 1eef08​: OUTPUT«Confused at line 11, near
"@​a.>>.say"â�¤current instr.​: 'perl6;HLL;Grammar;panic' pc 501 (ext/nqp-
rx/src/stage0/HLL-s0.pir​:327)â�¤Â»

�此�你身��康�天天快�
��亮

There's a passing test for this syntax in S03-metaops/hyper.t; Closing ticket.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Nov 14, 2013

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

@p6rt p6rt closed this as completed Nov 14, 2013
@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