X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=lib%2FCatalyst.pm;h=9d3040b9ca875e56dd09b97a1ff69d002b7f8e07;hp=7cc3184455d51d81d01656a7566ed749929bea4a;hb=4b48773e21725af46279b84f346f84c2e83ff6b9;hpb=a5d07d293f196ce3be5efa8eeead2231bbfb6304

diff --git a/lib/Catalyst.pm b/lib/Catalyst.pm
index 7cc3184..9d3040b 100644
--- a/lib/Catalyst.pm
+++ b/lib/Catalyst.pm
@@ -357,6 +357,13 @@ Almost the same as C<forward>, but does a full dispatch, instead of just
 calling the new C<$action> / C<$class-E<gt>$method>. This means that C<begin>,
 C<auto> and the method you go to are called, just like a new request.
 
+In addition both C<< $c->action >> and C<< $c->namespace >> are localized.
+This means, for example, that $c->action methods such as C<name>, C<class> and
+C<reverse> return information for the visited action when they are invoked
+within the visited action.  This is different from the behavior of C<forward>
+which continues to use the $c->action object from the caller action even when
+invoked from the callee.
+
 C<$c-E<gt>stash> is kept unchanged.
 
 In effect, C<visit> allows you to "wrap" another action, just as it