in reply to Re: how do you build and test your modules locally before publishing
in thread how do you build and test your modules locally before publishing

Huh? On my system at least, the perl option for setting a library path is an upper-case "i":

perl -Ilib t/00-load.t

That is, the same as prove. The lower-case "L" option (perl -l) is line end processing for one-liners.

prove -l (lower-case "L") is a useful shortcut for prove -Ilib.

perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'

Replies are listed 'Best First'.
Re^3: how do you build and test your modules locally before publishing
by davido (Cardinal) on Dec 31, 2012 at 17:21 UTC

    Corrected. ...sometimes things that are "force of habit" become difficult to explain. And somehow in so-doing, I managed to confuse myself. :) Thanks for the nudge.


    Dave