[Moose-commits] r7738 - Moose/trunk/lib/Moose/Manual

[autarch at code2.0beta.co.uk]

Author: autarch
Date: 2009-02-19 13:46:41 -0800 (Thu, 19 Feb 2009)
New Revision: 7738

Modified:
   Moose/trunk/lib/Moose/Manual/Types.pod
Log:
Remove MX::Types bits from types manual page


Modified: Moose/trunk/lib/Moose/Manual/Types.pod
===================================================================
--- Moose/trunk/lib/Moose/Manual/Types.pod	2009-02-19 21:44:11 UTC (rev 7737)
+++ Moose/trunk/lib/Moose/Manual/Types.pod	2009-02-19 21:46:41 UTC (rev 7738)
@@ -178,20 +178,11 @@
 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.
+"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.
 
-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);
-
 =head1 COERCION
 
 One of the most powerful features of Moose's type system is its