1 ---------------------------------------------------------------------
3 ---------------------------------------------------------------------
5 - clean up all ->initialize($_[0]) handling
7 (PARTIALLY DONE) - needs tests
9 We should always be sure that $_[0] is a package name, and not
12 - make &compute_all_applicable_attributes not return a HASH
16 All the info in the HASH is discoverable through the meta-object.
18 - General Purpose &clone_instance method
20 (PARTIALLY DONE) - need to implement the deep cloning & tests
22 It can be a method of the metaclass, like construct_instance is,
23 actually it should be called clone_instance, and it should
24 be thought of as a low-level cloning function, so it should not
25 do any blessing or anything of the sort. That is left for the
26 class to implement, as is the construct_instance.
28 - General Purpose &new_object and &clone_object method
30 (PARTIALLY DONE) - needs tests
32 I seem to be writing a new method each time, but since we dont
33 have a Object class to always inherit from, this is needed.
34 However, there is nothing to say that I cannot do something like:
36 Foo->meta->new_object(%params)
40 $foo->meta->clone_object($foo, %params)
42 Give it some more thought, but I think it is the best way to
45 - Role/Trait/Scalar-style mixin mechanism
47 This is fairly simple with the MOP, but the trick comes with
48 any SUPER:: calls. This will be a very tricky problem I think.
50 * see Class::Trait::Base, and maybe use anon-classes for this.
51 * review the Scalar model for mix-ins
52 * I like the Class does Role, Role isa Class from Perl 6 idea.
56 Should handle metaclass incompatibility issue, and do it through
57 class mixin composition.
59 - Prototype-style example
61 Make a C::MOP::Class subclass which has an AUTOLOAD method, the
62 method will DWIM depending up on the value it is passed.
64 Foo->prototype->say_hello(sub { print "Hello" });
66 This will turn into this:
68 Foo->prototype->add_method('say_hello' => sub { print "Hello" });
70 I am not sure how we should handle non-method arguments, mostly
71 because those would be static prototype variables, which would
72 translate to class package variables.
74 - Make a Class::MOP::Package
76 Class::MOP::Class would be a subclass of this, but I am not sure
77 this is worth the time.