From: Vincent Pit <vince@profvince.com>
Date: Sun, 3 Jan 2010 00:47:10 +0000 (+0100)
Subject: Add a link to Matt's blog post
X-Git-Tag: v0.20~9
X-Git-Url: http://git.vpit.fr/?a=commitdiff_plain;h=cf5208b77c6c9660f094662cc0f6d146f8b73121;p=perl%2Fmodules%2Findirect.git

Add a link to Matt's blog post
---

diff --git a/lib/indirect.pm b/lib/indirect.pm
index 96ff670..a5843ab 100644
--- a/lib/indirect.pm
+++ b/lib/indirect.pm
@@ -48,7 +48,9 @@ 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<swoosh> isn't defined, C<swoosh $x> actually compiles to C<< $x->swoosh >>).
+In L<http://www.shadowcat.co.uk/blog/matt-s-trout/indirect-but-still-fatal>, Matt S. Trout gives an example of an indirect construct that can cause a particularly bewildering error.
 
 It currently does not warn for core functions (C<print>, C<say>, C<exec> or C<system>).
 This may change in the future, or may be added as optional features that would be enabled by passing options to C<unimport>.