In this case, I might recommend using a .perldlrc file in the directory which can be used to do this on each load. Read more at, http://pdl.perl.org/?docs=perldl&title=the%20perldl%20manpage
I'm assuming putting `use blib;` in the file would be good enough? On Tue, Jul 17, 2012 at 1:39 PM, John Lapeyre <[email protected]> wrote: > On 07/17/2012 07:57 PM, Joel Berger wrote: >> I would seem that a command line switch would be nice, however your >> workaround is more verbose than needed. You should simply be able to >> `use blib` as if it were another script; this is what `-Mblib` does as >> a arguement to the perl interpreter. HTH > > I stopped searching online after `use lib './blib'` > failed ( `use lib './blib/lib'` would have worked ). > > But I'm quitting and restarting pdl2 repeatedly. When using > the uparrow to scroll through history, the cost of `use blib` and > `unshift @INC, './blib/lib'` is the same. Anyway I went back > to using a script for testing. > > I just wanted to make sure I wasn't overlooking some feature. > > >> >> Joel >> >> On Tue, Jul 17, 2012 at 12:38 PM, John Lapeyre >> <[email protected]> wrote: >>> >>> Hello, >>> >>> I can do this (and get what I expect): >>> >>>> pdl -Mblib >>> >>> But this fails and then prints the usage message: >>> >>>> pdl2 -Mblib >>> Unknown option: M >>> <snip> >>> >>> I can start pdl2 and unshift @INC, './blib/lib'. >>> But that is a little clumsy when iterating changes. >>> I searched around in docs, the web, and list archives, >>> but didn't find any talk about it. > _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
