X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FUpgrading.pod;h=048499037ed887127f539c7530ac89360e58bd13;hb=586c57d99badfbf772877206564f7041adb03ea9;hp=8a9993004c17917ffa6911ff38e5ac5f29970ce7;hpb=ade0097285a43b356dd4fd08b124f0839153de28;p=catagits%2FCatalyst-Runtime.git diff --git a/lib/Catalyst/Upgrading.pod b/lib/Catalyst/Upgrading.pod index 8a99930..0484990 100644 --- a/lib/Catalyst/Upgrading.pod +++ b/lib/Catalyst/Upgrading.pod @@ -1,3 +1,7 @@ +=head1 NAME + +Catalyst::Upgrading - Instructions for upgrading to the latest Catalyst + =head1 Upgrading to Catalyst 5.80 Most applications and plugins should run unaltered on Catalyst 5.80. @@ -39,7 +43,7 @@ Most common is the case of: use base qw/Component1 Component2/; And the Catalyst plugin most often causing this, is -L - if you are using this plugin +L - if you are using this plugin and see issues, then please upgrade! This can, however, be found in your own application - the only solution is to @@ -57,7 +61,7 @@ Moose components which say: to use the constructor provided by Moose, whilst working (if you do some hacks with the C< BUILDARGS > method), will not work with Catalyst 5.80 as C inherits from C, and so C< @ISA > fails -to linearise. +to linearize. The fix for this is to not inherit directly from C yourself. Having components which do not inherit their constructor from @@ -132,7 +136,7 @@ to use L to name the subroutine. Example: *$full_method_name = subname $full_method_name, sub { ... }; Additionally, you can take advantage of Catalysts use of L and -install the closure using the appropriate metaclass. Example: +install the closure using the appropriate meta class. Example: use Class::MOP; my $metaclass = Moose::Meta::Class->initialize($package_name); @@ -140,7 +144,7 @@ install the closure using the appropriate metaclass. Example: =head2 Hooking into application setup -To execute code during application startup the following snippet in MyApp.pm +To execute code during application start-up the following snippet in MyApp.pm used to work: sub setup { @@ -283,7 +287,7 @@ should change to using the public API, or, if you do not feel the public API adequately supports your use-case, please email the development list to discuss what API features you need so that you can be appropriately supported. -=head2 Class naming to packages defined does not correspond. +=head2 Class files with names that don't correspond to the packages they define In this version of Catalyst, if a component is loaded from disk, but no symbols are defined in that component's name space after it is loaded, this @@ -300,7 +304,7 @@ to B of the packages defined within that component. =head2 $c->plugin method -Calling the plugin method is deprecated, and calling it at runtime is B. Instead you are recommended to use L< Catalyst::Model::Adaptor > or similar to