From: Dave Rolsky <autarch@urth.org>
Date: Thu, 19 Feb 2009 21:46:41 +0000 (+0000)
Subject: Remove MX::Types bits from types manual page
X-Git-Tag: 0.71_01~17
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=bcc22289e33d7e1e197bc9864bbb3092978e236e;p=gitmo%2FMoose.git

Remove MX::Types bits from types manual page
---

diff --git a/lib/Moose/Manual/Types.pod b/lib/Moose/Manual/Types.pod
index fcb2d89..674d26d 100644
--- a/lib/Moose/Manual/Types.pod
+++ b/lib/Moose/Manual/Types.pod
@@ -178,19 +178,10 @@ you prefix names with some sort of namespace indicator to prevent
 these sorts of collisions.
 
 For example, instead of calling a type "PositiveInt", call it
-"MyApp::Type::PositiveInt" or "MyApp::Types::PositiveInt" - you may
-find it easiest to centralize these definitions in a lib/MyApp/Types.pm
-so the other classes in your application can simply do "use MyApp::Types"
-and assume that all relevant types have now been defined.
-
-The L<MooseX::Types> module provides namespaced types as functions so that
-you can import the names into packages and use them as barewords - i.e.
-
-  has 'foo' => (isa => 'MyApp::Types::PositiveInt');
-
-would become
-
-  has 'foo' => (isa => PositiveInt);
+"MyApp::Type::PositiveInt" or "MyApp::Types::PositiveInt". We
+recommend that you centralize all of these definitions in a single
+package, C<MyApp::Types>, which can be loaded by other classes in your
+application.
 
 =head1 COERCION