On Sun, Mar 30, 2008 at 10:56 PM, John W. Krahn <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >
> > On Mar 30, 6:54 am, [EMAIL PROTECTED] (John W. Krahn) wrote:
> >>
>
> >> die() exits the program.
> >>
> > Yes, I understand that die() exits the program. My question was are
> > you
[EMAIL PROTECTED] wrote:
On Mar 30, 6:54 am, [EMAIL PROTECTED] (John W. Krahn) wrote:
die() exits the program.
Yes, I understand that die() exits the program. My question was are
you able to process more than one line of code in a die() context?
die(), like print() and warn(), prints a li
On Mar 30, 6:54 am, [EMAIL PROTECTED] (John W. Krahn) wrote:
> That is usually written as:
>
> if ( @ARGV != 1 ) {
>
Good tip. Thank you.
> Why not pass $EX_USAGE to ExitScript() instead of using global $ExitStatus?
>
> ExitScript( $EX_USAGE );
Consistency is all. I try to get into a ha
[EMAIL PROTECTED] wrote:
Hey All!
Hello,
I've written a Bash script called `clock`, which is called by one of
two symbolic links: `clock-in` and `clock-out`. This script is,
effectively, a time-clock for tracking time spent on various projects
for clients. This script generates a "time card
On 24 Oct 2007 18:35:15 -, leo shen <[EMAIL PROTECTED]> wrote:
> Hi, I ran into "Inappropriate ioctl for device" when running the
> following two lines:
>
> my $file=shift @ARGV || File::Spec->catfile(q(.),q(a.res));
> open (INPUT,'<', $file) or die " can't open $file : $!";
Which line was it
