Re: A lil module creation advice

Is your module failing by being run or failing at compile time?

Every module that is 'used' must compile properly or the entire program will fail before it is run.

'use strict' will tell you exactly where the program is failing. Sending some debugging to the screen will tell you how much of the program is being run before failing.

mr greywolf

Comment on Re: A lil module creation advice

Replies are listed 'Best First'.
Re: Re: A lil module creation advice by snafu (Chaplain) on Apr 21, 2002 at 02:56 UTC
Well. This is a good question that I overlooked making clear when I started this thread. The program I am writing compiles just fine by itself. It even runs at runtime but the fact that my subs get executed at runtime when they should only be run when called is what's causing the whole script to fail. _ _ _ _ _ _ _ _ _ _ - Jim Insert clever comment here...	[reply]
Re: Re: A lil module creation advice by snafu (Chaplain) on Apr 22, 2002 at 17:05 UTC
Hmm. I thought I submitted a reply to this one already but I must have overlooked the submit button a few days. Anyhoo, just so everyone knows... I was using strict; as I always do, religiously. I learned my lesson on that one way back at the beginning of my Perl coding days. This suggestion from greywolf, btw, is always an excellent suggestion, nay, rule! The script in question was compiling fine by itself. Thanks for the input everyone. I just needed to make those two points clear so that at least people knew I wasn't a total tard :) _ _ _ _ _ _ _ _ _ _ - Jim Insert clever comment here...	[reply]


Pathologically Eclectic Rubbish Lister
	PerlMonks