1Catalyst::Delta(3) User Contributed Perl Documentation Catalyst::Delta(3)
2
3
4
6 Catalyst::Delta - Overview of changes between versions of Catalyst
7
9 This is an overview of the user-visible changes to Catalyst in version
10 5.8.
11
12 Deprecations
13 Please see Catalyst::Upgrading for a full description of how changes in
14 the framework may affect your application.
15
16 Below is a brief list of features which have been deprecated in this
17 release:
18
19 ::[MVC]:: style naming scheme has been deprecated and will warn
20 NEXT is deprecated for all applications and components, use MRO::Compat
21 Dispatcher methods which are an implementation detail made private,
22 public versions now warn.
23 MyApp->plugin method is deprecated, use Catalyst::Model::Adaptor
24 instead.
25 __PACKAGE__->mk_accessors() is supported for backward compatibility
26 only, use Moose attributes instead in new code.
27 Use of Catalyst::Base now warns
28
29 New features
30 Dispatcher
31
32 Fix forwarding to Catalyst::Action objects.
33 Add the dispatch_type method
34
35 Restarter
36
37 The development server restarter has been improved to be compatible
38 with immutable Moose classes, and also to optionally use
39 B::Hooks::OP::Check::StashChange to handle more complex application
40 layouts correctly.
41
42 $c->uri_for_action method.
43
44 Give a private path to the Catalyst action you want to create a URI
45 for.
46
47 Logging
48
49 Log levels have been made additive.
50
51 Catalyst::Test
52
53 Change to use Sub::Exporter.
54 Support mocking multiple virtual hosts
55 New methods like action_ok and action_redirect to write more compact
56 tests
57
58 Catalyst::Response
59
60 · New print method which prints @data to the output stream, separated
61 by $,. This lets you pass the response object to functions that
62 want to write to an IO::Handle.
63
64 · Added code method as an alias for "$res->status"
65
66 Consequences of the Moose back end
67 · Components are fully compatible with Moose, and all Moose features,
68 such as method modifiers, attributes, roles, BUILD and BUILDARGS
69 methods are fully supported and may be used in components and
70 applications.
71
72 · Many reusable extensions which would previously have been plugins
73 or base classes are better implemented as Moose roles.
74
75 · MooseX::MethodAttributes::Inheritable is used to contain action
76 attributes. This means that attributes are represented in the MOP,
77 and decouples action creation from attributes.
78
79 · There is a reasonable API in Catalyst::Controller for working with
80 and registering actions, allowing a controller sub-class to replace
81 subroutine attributes for action declarations with an alternate
82 syntax.
83
84 · Refactored capturing of $app from Catalyst::Controller into
85 Catalyst::Component::ApplicationAttribute for easier reuse in other
86 components.
87
88 · Your application class is forced to become immutable at the end of
89 compilation.
90
91 Bug fixes
92 · Don't ignore SIGCHLD while handling requests with the development
93 server, so that system() and other ways of creating child processes
94 work as expected.
95
96 · Fixes for FastCGI when used with IIS 6.0
97
98 · Fix a bug in uri_for which could cause it to generate paths with
99 multiple slashes in them.
100
101 · Fix a bug in Catalyst::Stats, stopping garbage being inserted into
102 the stats if a user calls begin => but no end
103
104
105
106perl v5.12.1 2009-11-22 Catalyst::Delta(3)