From: Brad Bowman <bsb@strategicdata.com.au>
Date: Wed, 28 Sep 2011 07:59:43 +0000 (+1000)
Subject: BestPractices namespace::autoclean not "no Moose"
X-Git-Tag: 2.0301~14
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=d5cb877febe9ec232ebc168d181f3750a0616dbd;p=gitmo%2FMoose.git

BestPractices namespace::autoclean not "no Moose"

Make clear that namespace::autoclean replaces the often seen
use of "no Moose".
---

diff --git a/lib/Moose/Manual/BestPractices.pod b/lib/Moose/Manual/BestPractices.pod
index 5840910..0f7445e 100644
--- a/lib/Moose/Manual/BestPractices.pod
+++ b/lib/Moose/Manual/BestPractices.pod
@@ -36,7 +36,8 @@ definitions by making your class immutable.
 The C<use namespace::autoclean> bit is simply good code hygiene, as it removes
 imported symbols from  you class's namespace at the end of your package's
 compile cycle, including Moose keywords.  Once the class has been
-built, these keywords are not needed.
+built, these keywords are not needed.  (This is the preferred to placing
+C<no Moose> at the end of your package).
 
 The C<make_immutable> call allows Moose to speed up a lot of things, most
 notably object construction. The trade-off is that you can no longer change