On Jul 25, Stephanie Stiavetti said:
>open (REZFILE, "$>>rezFile") or die "ew! can't open $rezFile! $!\n";
>
> foreach (@allParams) {
> print "$_\t";
> }
> print "\n\n";
>
> close (REZFILE);
I would check to see if the file could be closed properly. And maybe even
check each of those prints().
eval {
open FILE, ">> $file" or die "can't open $file: $!";
for (@things) {
print FILE or die "can't print to $file: $!";
}
close FILE or die "can't close $file: $!";
};
if ($@) {
# something broke
}
else {
# things are ok
}
--
Jeff "japhy" Pinyan [EMAIL PROTECTED] http://www.pobox.com/~japhy/
I am Marillion, the wielder of Ringril, known as Hesinaur, the Winter-Sun.
Are you a Monk? http://www.perlmonks.com/ http://forums.perlguru.com/
Perl Programmer at RiskMetrics Group, Inc. http://www.riskmetrics.com/
Acacia Fraternity, Rensselaer Chapter. Brother #734
** Manning Publications, Co, is publishing my Perl Regex book **
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: checking for true/false after a command has run
Jeff 'japhy/Marillion' Pinyan Wed, 25 Jul 2001 12:46:58 -0700
- checking for true/false after a command has ... Stephanie Stiavetti
- Cooperating with WINSOCK using Socket:: Dan Grossman
- Re: checking for true/false after a com... Jeff 'japhy/Marillion' Pinyan
- Re: checking for true/false after a com... Chris Milligan
- Re: checking for true/false after a... Michael Fowler
- Re: checking for true/false after a com... Perl Person
- Re: checking for true/false after a com... Michael Fowler
- RE: checking for true/false after a com... Stephanie Stiavetti
- Re: checking for true/false after a... Michael Fowler
- Re: checking for true/false after a... Stephen P. Potter
