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

LTA error message on an unrecognized declarator #1742

Closed
p6rt opened this issue May 3, 2010 · 7 comments
Closed

LTA error message on an unrecognized declarator #1742

p6rt opened this issue May 3, 2010 · 7 comments
Labels

Comments

@p6rt
Copy link

p6rt commented May 3, 2010

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

Searchable as RT74866$

@p6rt
Copy link
Author

p6rt commented May 3, 2010

From @sorear

02​:07 < sorear> rakudo​: module Soric4​::Event; macro foo is parsed( 0 ) { }
02​:07 <+p6eval> rakudo c4857a​: OUTPUT«Confused at line 11, near "module
  Sor"␤current instr.​: 'perl6;HLL;Grammar;panic' pc 500
  (ext/nqp-rx/src/stage0/HLL-s0.pir​:328)␤»

Adding a page of comments between the module statement and the attempted
macro definition did not change the result, ie "Sor" was still blamed.
Most confusingly, this error message to me implies a lexical problem in
the middle of the identifier. If, as masak suggests, context is being
limited for space reasons, displaying complete words would improve this
error case a lot.

@p6rt
Copy link
Author

p6rt commented Jul 20, 2010

From @jnthn

On Mon May 03 02​:19​:31 2010, stefanor@​cox.net wrote​:

02​:07 < sorear> rakudo​: module Soric4​::Event; macro foo is parsed( 0 ) { }
02​:07 <+p6eval> rakudo c4857a​: OUTPUT«Confused at line 11, near "module
Sor"␤current instr.​: 'perl6;HLL;Grammar;panic' pc 500
(ext/nqp-rx/src/stage0/HLL-s0.pir​:328)␤»

Now​:

module Soric4​::Event; macro foo is parsed( 0 ) { }
Macros are not yet implemented at line 1, near " foo is pa"

Which is rather more informative. I think this ticket brings up some
bigger issues, though this is a decent improvement for valid but not yet
implemented declarators. Also added similar for scope declarator state
and type declarator constant in case we don't get to some support for
them pre-R*.

Jonathan

@p6rt
Copy link
Author

p6rt commented Jul 20, 2010

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

@p6rt
Copy link
Author

p6rt commented May 11, 2013

From @coke

On Mon Jul 19 18​:57​:07 2010, jnthn@​jnthn.net wrote​:

On Mon May 03 02​:19​:31 2010, stefanor@​cox.net wrote​:

02​:07 < sorear> rakudo​: module Soric4​::Event; macro foo is parsed( 0 ) { }
02​:07 <+p6eval> rakudo c4857a​: OUTPUT«Confused at line 11, near "module
Sor"␤current instr.​: 'perl6;HLL;Grammar;panic' pc 500
(ext/nqp-rx/src/stage0/HLL-s0.pir​:328)␤»

Now​:

module Soric4​::Event; macro foo is parsed( 0 ) { }
Macros are not yet implemented at line 1, near " foo is pa"

Which is rather more informative. I think this ticket brings up some
bigger issues, though this is a decent improvement for valid but not yet
implemented declarators. Also added similar for scope declarator state
and type declarator constant in case we don't get to some support for
them pre-R*.

Jonathan

Behavior changed again​:

00​:57 < [Coke]> rakudo​: module Soric4​::Event; macro foo is parsed( 0 ) { }
00​:58 <+camelia> rakudo bfd850​: OUTPUT«===SORRY!===␤Cannot call
  'trait_mod​:<is>'; none of these signatures match​:␤​:(Mu​:U
  $child, Mu​:U $parent)␤​:(Mu​:U $type, :rw(​:$rw)!)␤​:(Mu​:U $type,
  :nativesize(​:$nativesize)!)␤​:(Mu​:U $type,
  :hidden(​:$hidden)!)␤​:(Mu​:U $type, *%fail)␤​:(Attribute​:D $attr…

Is this better?

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Feb 8, 2015

From @Mouq

I'm not sure this ticket is valid anymore. It's about declarators not
throwing NYI errors, and as far as I can tell the only declarator that
Rakudo doesn't know about at this point in time is the "quote qX"
declarator listed in S03, which seems to simply be a fossil, as S06
indicates something more like "sub quote​:<qX> {...}".

This ticket appears to be resolvable, pending further discussion.

On Fri May 10 21​:59​:03 2013, coke wrote​:

On Mon Jul 19 18​:57​:07 2010, jnthn@​jnthn.net wrote​:

On Mon May 03 02​:19​:31 2010, stefanor@​cox.net wrote​:

02​:07 < sorear> rakudo​: module Soric4​::Event; macro foo is parsed(
0 ) { }
02​:07 <+p6eval> rakudo c4857a​: OUTPUT«Confused at line 11, near
"module
Sor"␤current instr.​: 'perl6;HLL;Grammar;panic' pc
500
(ext/nqp-rx/src/stage0/HLL-s0.pir​:328)␤»

Now​:

module Soric4​::Event; macro foo is parsed( 0 ) { }
Macros are not yet implemented at line 1, near " foo is pa"

Which is rather more informative. I think this ticket brings up some
bigger issues, though this is a decent improvement for valid but not
yet
implemented declarators. Also added similar for scope declarator
state
and type declarator constant in case we don't get to some support for
them pre-R*.

Jonathan

Behavior changed again​:

00​:57 < [Coke]> rakudo​: module Soric4​::Event; macro foo is parsed( 0 )
{ }
00​:58 <+camelia> rakudo bfd850​: OUTPUT«===SORRY!===␤Cannot call
'trait_mod​:<is>'; none of these signatures
match​:␤​:(Mu​:U
$child, Mu​:U $parent)␤​:(Mu​:U $type,
:rw(​:$rw)!)␤​:(Mu​:U $type,
:nativesize(​:$nativesize)!)␤​:(Mu​:U $type,
:hidden(​:$hidden)!)␤​:(Mu​:U $type,
*%fail)␤​:(Attribute​:D $attr…

Is this better?

@p6rt
Copy link
Author

p6rt commented Mar 28, 2015

From @jnthn

On Sat Feb 07 19​:06​:30 2015, Mouq wrote​:

I'm not sure this ticket is valid anymore. It's about declarators not
throwing NYI errors, and as far as I can tell the only declarator that
Rakudo doesn't know about at this point in time is the "quote qX"
declarator listed in S03, which seems to simply be a fossil, as S06
indicates something more like "sub quote​:<qX> {...}".

This ticket appears to be resolvable, pending further discussion.

Agree; resolving.

@p6rt p6rt closed this as completed Mar 28, 2015
@p6rt
Copy link
Author

p6rt commented Mar 28, 2015

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

@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