p5-mop-redux
p5-mop-redux copied to clipboard
stevan
A(nother) MOP for Perl 5
This should probably just follow along with whatever the core subroutine signatures does, but it would potentially be a not-insignificant speedup to not provide it (assuming a signature is specified).
``` 17:42 stevan: just getting sick of stuff like 17:42 stevan: package Foo { class Bar extends Foo::Baz { ... } } 17:42 stevan: in Bar.pm 17:42 doy: yeah, that...
This has precedence with `DESTROY` - leaving the `sub` off of `DESTROY` methods works in existing perl classes. Should leaving `method` off of `BUILD` and `DEMOLISH` work similarly? This should...
`import` isn't really a method, and can cause all kinds of confusing problems if you try to treat it as one. `DESTROY` should be handled by `DEMOLISH`/`DEMOLISHALL`. Should defining these...
This was always the intent (it matches how other features like given/when work), but lexical exporting doesn't currently play well with Devel::CallParser. I've reported the bug to Zefram, but it...
Looks like we need mop::manual::details::meta soon :) domm on IRC #p5-mop was asking about it earlier, and I'm wondering too... I'm gonna dig in and maybe try writing some stuff;...
Given this situation: ``` perl # Foo/Bar/Baz.pm package Foo::Bar; use mop; class Baz extends Foo::Bar { } no mop; ``` ``` perl # Foo/Bar.pm package Foo; use mop; class Bar...
This is slightly related to #95. There are a lot more things that metaclasses have in common than just the `fire`/`bind` stuff - class, role, attribute, and method all have...
Given this code: ``` perl class MetaFoo extends mop::class { } class MetaBar extends mop::class { } class Foo meta MetaFoo { } class Bar extends Foo meta MetaBar {...