From: Vincent Pit <vince@profvince.com>
Date: Thu, 4 Jun 2009 21:43:01 +0000 (+0200)
Subject: Use a better metasyntactic name instead of C<sub>
X-Git-Tag: v0.14~2
X-Git-Url: http://git.vpit.fr/?a=commitdiff_plain;h=7ac06f9de99a3422ab7ea4067d289e6038399970;p=perl%2Fmodules%2Findirect.git

Use a better metasyntactic name instead of C<sub>
---

diff --git a/lib/indirect.pm b/lib/indirect.pm
index b8e6f84..9edc23e 100644
--- a/lib/indirect.pm
+++ b/lib/indirect.pm
@@ -46,7 +46,7 @@ BEGIN {
 =head1 DESCRIPTION
 
 When enabled (or disabled as some may prefer to say, since you actually turn it on by calling C<no indirect>), this pragma warns about indirect object syntax constructs that may have slipped into your code.
-This syntax is now considered harmful, since its parsing has many quirks and its use is error prone (when C<sub> isn't defined, C<sub $x> is actually interpreted as C<< $x->sub >>).
+This syntax is now considered harmful, since its parsing has many quirks and its use is error prone (when C<swoosh> isn't defined, C<swoosh $x> actually compiles to C<< $x->swoosh >>).
 
 It currently does not warn when the object is enclosed between braces (like C<meth { $obj } @args>) or for core functions (C<print> or C<say>).
 This may change in the future, or may be added as optional features that would be enabled by passing options to C<unimport>.