From: Karen Etheridge Date: Sat, 8 Sep 2012 19:13:44 +0000 (-0700) Subject: I<> markup X-Git-Tag: v1.004002~3^2~2 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=9a363fed302e7c3fdeb2663a10a882a7d70cfa0e;p=p5sagit%2Fstrictures.git I<> markup --- diff --git a/lib/strictures.pm b/lib/strictures.pm index 913198f..8d78507 100644 --- a/lib/strictures.pm +++ b/lib/strictures.pm @@ -197,16 +197,16 @@ help. For example, foo { ... }; where foo is an & prototyped sub that you forgot to import - this is -pernicious to track down since all -seems- fine until it gets called +pernicious to track down since all I fine until it gets called and you get a crash. Worse still, you can fail to have imported it due to a circular require, at which point you have a load order dependent -bug which I've seen before now -only- show up in production due to tiny +bug which I've seen before now I show up in production due to tiny differences between the production and the development environment. I wrote L to explain this particular problem before L itself existed. As such, in my experience so far the L extra testing has --avoided- production versus development differences, not caused them. +I production versus development differences, not caused them. Additionally, L' policy is very much "try and provide as much protection as possible for newbies - who won't think about whether there's