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

Null PMC access when using ordinary operator after defining custom multi variant in Rakudo #1055

Closed
p6rt opened this issue Jun 12, 2009 · 6 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Jun 12, 2009

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

Searchable as RT66552$

@p6rt
Copy link
Author

p6rt commented Jun 12, 2009

From @masak

<masak> rakudo​: role A {}; multi sub infix​:<==>(A $a, A $b) {}; 42 == 42
<p6eval> rakudo e61569​: OUTPUT«Null PMC access in find_method() [...]
* masak submits rakudobug

@p6rt
Copy link
Author

p6rt commented Jun 12, 2009

From @moritz

On Fri Jun 12 05​:49​:17 2009, masak wrote​:

<masak> rakudo​: role A {}; multi sub infix​:<==>(A $a, A $b) {}; 42 == 42
<p6eval> rakudo e61569​: OUTPUT«Null PMC access in find_method() [...]
* masak submits rakudobug

Now tested in t/spec/S06-operator-overloading/sub.t.

Cheers,
Moritz

@p6rt
Copy link
Author

p6rt commented Jun 12, 2009

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

@p6rt
Copy link
Author

p6rt commented Jun 23, 2009

From amoc.yn@gmail.com

at rev​: 10f2235028194deddf3db350b5a4a5208484ac09
relative ticket​: [perl #​65638]
it's url​: http://rt.perl.org/rt3/Public/Bug/Display.html?id=65638

## "multi sub" works

multi sub infix​:<op> ($l,$r) { $l ~ $r }; say( 1 op 2 )
12

## overiding works (but doesn't warn that it is overiding builtin op)

sub infix​:<+> ($l,$r) { $l ~ $r }; say( 1 + 2 )
12

## meanwhile, it occurs Null PMC access

multi sub infix​:<+> ($l,$r) { $l ~ $r }; say( 1 + 2 )
Null PMC access in find_method()
in Main (<unknown>​:1)

@p6rt
Copy link
Author

p6rt commented Mar 23, 2010

From @ShimmerFairy

The posted test (the bug-related additions to it) passes, and the posted
problems do not return a Null PMC access.
Bug resolved.
--
Don't Panic!

@p6rt
Copy link
Author

p6rt commented Mar 23, 2010

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

@p6rt p6rt closed this as completed Mar 23, 2010
@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