> Wiggins d'Anconia wrote:
> > Please bottom post....
> > 
> > J Adam Latham wrote:
> > 
> >> Try removing "my" from all the variables in your module ... You're 
> >> privatizing them to your module thereby excluding them from your 
> >> external program ...
> >> At least that's my guess! :^)
> >>
> > 
> > Hopefully you could at least suggest to 'our' them instead of 'my', so 
> > that 'strict' checking can remain in play, as it should remain in
play....
> > 
> > perldoc -f our
> > 
> > In general this is where drieux would interject his ramblings about how 
> > you have reached a point where you probably want to brew your own
module 
> > (check the list archives for such rantings which are usually very 
> > informative), which is simple enough to do.
> > 
> > I would suggest reading up on creating your own module,
> > 
> > perldoc perlmod
> > perldoc perlmodlib
> > perldoc -f package
> > perldoc -f use
> > perldoc Exporter
> > 
> > Essentially you create a separate file, a .pm, throw a package
statement 
> > in there, make it an Exporter if you so desire, 'our' a few variables, 
> > then in your scripts you simply 'use' it.  Back in business.... when
you 
> > get stuck ask more questions.
> 
> I figured that would be the answer. I've created custom modules
before. I was 
> just being lazy and didn't want to create a module and place it in one
of the 
> @INC directories ;)
> 

No need to use @INC directories.

perldoc lib
perldoc FindBin

http://danconia.org


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>


Reply via email to