From: Tomas Doran Date: Fri, 20 Feb 2009 16:58:08 +0000 (+0000) Subject: I always got full marks on spelling tests when I was a kid... Ok, I'm full of lies... X-Git-Tag: 5.80001~80 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=commitdiff_plain;h=ba03ccca234d713ad0406e0377a24d0431a4f0bb I always got full marks on spelling tests when I was a kid... Ok, I'm full of lies, I can't spell for sh*t. --- diff --git a/lib/Catalyst/Upgrading.pod b/lib/Catalyst/Upgrading.pod index d03cef6..d335936 100644 --- a/lib/Catalyst/Upgrading.pod +++ b/lib/Catalyst/Upgrading.pod @@ -5,10 +5,10 @@ Most applications and plugins should run unaltered on Catalyst 5.80. However as a lot of refactoring work has taken place, and several changes have been made which could cause incompatibilities. If your application or plugin is using deprecated code, or relying on side-effects, then you could have -issues upgrding to this release. +issues upgrading to this release. Most issues found with pre-existing components have been easy to solve, and a -complete description of behavior changes which may cause compatibility issues, +complete description of behaviour changes which may cause compatibility issues, or warnings which are now emitted is included below to help if you have problems. If you think you have found an upgrade related issue which is not covered in @@ -51,7 +51,7 @@ compatible way is: use Moose; BEGIN { extends 'Catalyst::Component' }; # Or ::Controller, or whatever -Note that the C< extends > decleration needs to occur in a begin block for +Note that the C< extends > declaration needs to occur in a begin block for L to operate correctly. You also don't get the L constructor, and therefore attribute initialization will not work as normally expected. If you want to use Moose attributes, then they need to be made lazy @@ -152,7 +152,7 @@ inside Moose. Previously, writing to a class data accessor would copy the accessor method down into your package. -This behavior has been removed. Whilst the class data is still stored +This behaviour has been removed. Whilst the class data is still stored per-class, it is stored on the metaclass of the class defining the accessor. Therefore anything relying on the side-effect of the accessor being copied down @@ -182,8 +182,8 @@ The following test demonstrates the problem: Previously, it was possible to add additional accessors to Catalyst::Request (or other classes) by calling the mk_accessors class method. -This is no longer supported - users should make a sub-class of the class whos -behavior they would like to change, rather than globally polluting the +This is no longer supported - users should make a sub-class of the class whose +behaviour they would like to change, rather than globally polluting the Catalyst objects. =head2 Confused multiple inheritance with Catalyst::Component::COMPONENT @@ -193,7 +193,7 @@ right hand side, which could then delegate back again with NEXT. This (as it is insane AND makes no sense with C3 method dispatch order), and is therefore no longer supported. -If a COMPONENT method is detected in the inheritence hierarchy to the right +If a COMPONENT method is detected in the inheritance hierarchy to the right hand side of Catalyst::Component::COMPONENT, then the following warning message will be emitted: @@ -235,15 +235,15 @@ The first time one of these methods is called, a warning will be emitted: You should B be calling any of these methods from application code. -Plugins authors and maintainers whos plugins currently call these methods +Plugins authors and maintainers whose plugins currently call these methods should change to using the public API, or, if you do not feel the public API -adaquately supports your use-case, please email the development list to +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. In this version of Catalyst, if a component is loaded from disk, but no -symbols are defined in that component's namespace after it is loaded, this +symbols are defined in that component's name space after it is loaded, this warning will be issued: require $class was successful but the package is not defined. @@ -261,7 +261,7 @@ 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 -compose the functionality you need outside of the main application namespace. +compose the functionality you need outside of the main application name space. Calling the plugin method at runtime will not be supported past Catalyst 5.81.