use strict;
use warnings;
-use Test::More tests => 16;
+use Test::More tests => 24;
use Test::Exception;
BEGIN {
}
my $anon_class_id;
+my $instance;
{
my $anon_class = Class::MOP::Class->create_anon_class();
isa_ok($anon_class, 'Class::MOP::Class');
lives_ok {
$anon_class->add_method('foo' => sub { "__ANON__::foo" });
} '... added a method to my anon-class';
- ok($anon_class->has_method('foo'), '... we have a foo method now');
+ ok($anon_class->has_method('foo'), '... we have a foo method now');
- my $instance = $anon_class->new_object();
+ $instance = $anon_class->new_object();
isa_ok($instance, $anon_class->name);
isa_ok($instance, 'Foo');
ok(!exists $main::Class::MOP::Class::__ANON__::SERIAL::{$anon_class_id . '::'}, '... the package no longer exists');
+# the superclass relationship actually
+# still exists for the instance ...
+isa_ok($instance, 'Foo');
+
+# and oddly enough we can still
+# call methods on our instance
+can_ok($instance, 'foo');
+can_ok($instance, 'bar');
+
+is($instance->foo, '__ANON__::foo', '... got the right return value of our foo method');
+is($instance->bar, 'Foo::bar', '... got the right return value of our bar method');
+
+# but it breaks down when we try to create another one ...
+
+my $instance_2 = bless {} => ref($instance);
+isa_ok($instance_2, ref($instance));
+ok(!$instance_2->isa('Foo'), '... but the new instance is not a Foo');
+ok(!$instance_2->can('foo'), '... and it can no longer call the foo method');
+
# NOTE:
# I bumped this test up to 100_000 instances, and
# still got not conflicts. If your application needs