[Moose-commits] r7633 - Moose/trunk/lib/Moose/Cookbook/Extending

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

Author: autarch
Date: 2009-02-12 09:01:25 -0800 (Thu, 12 Feb 2009)
New Revision: 7633

Modified:
   Moose/trunk/lib/Moose/Cookbook/Extending/Recipe3.pod
Log:
Apparentl S<C<< doesn't work with all pod parsers


Modified: Moose/trunk/lib/Moose/Cookbook/Extending/Recipe3.pod
===================================================================
--- Moose/trunk/lib/Moose/Cookbook/Extending/Recipe3.pod	2009-02-12 16:59:47 UTC (rev 7632)
+++ Moose/trunk/lib/Moose/Cookbook/Extending/Recipe3.pod	2009-02-12 17:01:25 UTC (rev 7633)
@@ -42,13 +42,13 @@
 output every time a new object is created, but you can think of some
 more interesting things to do with your own base class.
 
-This uses the magic of L<Moose::Exporter>. When we call S<C<<
-Moose::Exporter->setup_import_methods( also => 'Moose' ) >>> it builds
-C<import> and C<unimport> methods for you. The S<C<< also => 'Moose'
->>> bit says that we want to export everything that Moose does.
+This uses the magic of L<Moose::Exporter>. When we call C<<
+Moose::Exporter->setup_import_methods( also => 'Moose' ) >> it builds
+C<import> and C<unimport> methods for you. The C<< also => 'Moose' >>
+bit says that we want to export everything that Moose does.
 
 The C<import> method that gets created will call our C<init_meta>
-method, passing it S<C<< for_caller => $caller >>> as its
+method, passing it C<< for_caller => $caller >> as its
 arguments. The C<$caller> is set to the class that actually imported
 us in the first place.