die

How can I run a system command and die if anything is written to STDERR?

由 天涯浪子 提交于 2019-12-20 04:27:08
问题 I'm writing a Perl script which uses an external script. The external script must run from a specific directory so I found the following useful: use IPC::System::Simple qw(capture); my @args = ('external script path...', 'arg1', ...); my $out = capture( [0], "cd $dir ; @args" ); Sometimes the external script writes stuff to STDERR but still returns 0. I wish to capture these times and confess (or die ). Since I don't control the return value of the external script, I thought maybe I could

What is the difference between echo('exit'); die; and die('exit');?

由 匆匆过客 提交于 2019-12-19 06:28:33
问题 I have seen some code do this: if(something){ echo 'exit from program'; die; } ...more code And others that just use die : if(something) die('exit from program'); ...more code Is there any inherent difference in when it would end the program, should I be aware of the code that comes after it? etcetera UPDATE I am asking mainly, if it is a coding style, or if there is a real reason why some is coded one way versus another. I am not asking what the difference between exit and die is. 回答1: No,

How can I get around a 'die' call in a Perl library I can't modify?

由 为君一笑 提交于 2019-12-17 22:27:11
问题 Yes, the problem is with a library I'm using, and no, I cannot modify it. I need a workaround. Basically, I'm dealing with a badly written Perl library, that exits with 'die' when a certain error condition is encountered reading a file. I call this routine from a program which is looping through thousands of files, a handful of which are bad. Bad files happen; I just want my routine to log an error and move on. IF I COULD modify the library, I would simply change the die "error"; to a print

Can a Perl system() call ever die?

由 戏子无情 提交于 2019-12-12 10:36:27
问题 Can a system() call can ever die in Perl 5? (in other words, in order to 100% crash-proof a program that does a system() call, does it need to be wrapped into an eval block , or is that wholly totally unnecessary?) I haven't found a single mention to that possibility in perldoc system, but didn't quite find the precise "this call never dies" either. NOTE: the question is about basic CORE Perl here, no autodie or any other custom module that would have similar effect. Also, assume no ALRM

How can I redirect output of die function to a file in Perl?

由 a 夏天 提交于 2019-12-12 08:46:29
问题 I want to redirect the die messages to a separate file so that I can compare that file later to determine what went wrong. But this code gives me errors: $ cat test.pl use strict; use warnings; my $log = "msglog.log"; die $log "DEAD$!"; $ perl test.pl Missing comma after first argument to die function at test.pl line 5, near ""DEAD$!";" Execution of test.pl aborted due to compilation errors. $ I do not want to do a 2> from the caller. Is there someway to redirect them from within the script?

Need to abort a perl script (make it die) - from another script.

由 ぐ巨炮叔叔 提交于 2019-12-12 00:22:46
问题 I need to abort a Perl script which is running in the background from another script. Many perl scripts run on our machine. I need to abort one of the them on request. All I will know is the name of the perl script to abort. I need to abort that one particular script without affecting other processes. I tried killing it using PID/Image Name but it did not work for the below reasons, 1)I do not know the PID of the script (as it runs from a trigger) 2)The script runs in the background, so the

NetLogo: n-of error when all turtles die

由 [亡魂溺海] 提交于 2019-12-11 20:51:24
问题 I have a simulation where turtles walk onto red patches and die, which works, but everything that has n-of in it reports an error as soon as most of/all turtles are dead. I do understand the error, since the simulation tries to get n-of while there is no turtle left, but how do i fix that? Is there a way to use n-of when at the end of the simulation all the turtles are dead? If there is, how do I do it?, and if not, is there an alternative way to making the turtles die on red patches? My

php OOP Exceptions or die()?

由 岁酱吖の 提交于 2019-12-10 10:47:10
问题 I am developing some project. And I want to control different errors. I know that in all popular frameworks and php projects there are different Exceptions. But I think that is not required work. If the error is occured we can make die() with our message. 1. What are the main pluses of Exceptions? 2. Can I control my errors with die()? Thank you. 回答1: Well, you could use die() . But that makes all errors fatal. Meaning that you cannot try to recover from the error at all. In some cases that's

php OOP Exceptions or die()?

由 ↘锁芯ラ 提交于 2019-12-06 08:47:31
I am developing some project. And I want to control different errors. I know that in all popular frameworks and php projects there are different Exceptions. But I think that is not required work. If the error is occured we can make die() with our message. 1. What are the main pluses of Exceptions? 2. Can I control my errors with die()? Thank you. Well, you could use die() . But that makes all errors fatal. Meaning that you cannot try to recover from the error at all. In some cases that's fine to do. But in most cases, you may want the ability to "clean up" after the error, or to try another

How can I redirect output of die function to a file in Perl?

由 霸气de小男生 提交于 2019-12-04 04:02:13
I want to redirect the die messages to a separate file so that I can compare that file later to determine what went wrong. But this code gives me errors: $ cat test.pl use strict; use warnings; my $log = "msglog.log"; die $log "DEAD$!"; $ perl test.pl Missing comma after first argument to die function at test.pl line 5, near ""DEAD$!";" Execution of test.pl aborted due to compilation errors. $ I do not want to do a 2> from the caller. Is there someway to redirect them from within the script? wkl Perl's die prints to STDERR so you could redirect STDERR to a file. #!/usr/bin/env perl # the path
订阅 die