From 090b242d8855067df4a532a2112c53bc8cc2b83a Mon Sep 17 00:00:00 2001
From: Brian Phillips <brian@thephillips.info>
Date: Thu, 3 Mar 2011 12:18:50 -0800
Subject: Add caveat about modifying @ISA after calling extends

---
 lib/MooseX/NonMoose.pm | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'lib')

diff --git a/lib/MooseX/NonMoose.pm b/lib/MooseX/NonMoose.pm
index dd66b92..0fd9282 100644
--- a/lib/MooseX/NonMoose.pm
+++ b/lib/MooseX/NonMoose.pm
@@ -101,6 +101,11 @@ any class. For globref-based classes in particular, L<MooseX::GlobRef> will
 also allow Moose to work. For more information, see the C<032-moosex-insideout>
 and C<033-moosex-globref> tests bundled with this dist.
 
+=item * Modifying your class' C<@ISA> after an intial C<extends> call will potentially
+cause problems if any of those new entries in the C<@ISA> override the constructor.
+C<MooseX::NonMoose> wraps the nearest C<new()> method at the time C<extends>
+is called and will not see any other C<new()> methods in the @ISA hierarchy.
+
 =item * Completely overriding the constructor in a class using
 C<MooseX::NonMoose> (i.e. using C<sub new { ... }>) currently doesn't work,
 although using method modifiers on the constructor should work identically to
-- 
cgit v1.2.3