I have thought about it, maybe you are right in many cases. But overloading Perl built-in is just wanted in some situations also. So I update the module last ngiht. Now the module have two sub named "system" and "system_ex", users can take what they prefer. Thanks for your advice.
2011/6/2 brian d foy <brian.d....@gmail.com> > [[ This message was both posted and mailed: see > the "To," "Cc," and "Newsgroups" headers for details. ]] > > In article <banlktinbn2jwod545vaxm80rjc6rbh1...@mail.gmail.com>, ��谨 > <yikuyiku....@gmail.com> wrote: > > > This module is to help people handle these things. > > I guess some lazy boys want the module maybe.It`s really troublesome > adding > > a alarm() after every system(), especially in a exist big program. > > Well, that' s a problem of architecture. It's easy to make a subroutine > that wraps all of this. My only concern is you using a sub name with > the same name as a Perl built-in. > > > This module will handle everything, include timeout, local %SIG,$@,right > > exit code,etc. > > Boys only use System::Timeout.all done. > > I guess it help people saving SIGALRM for something else too. > > In that case, don't overload system(). > > -- > brian d foy (one of many PAUSE admins), http://pause.perl.org > PAUSE instructions: > http://pause.perl.org/pause/query?ACTION=pause_04about > Archives: http://www.xray.mpe.mpg.de/mailing-lists/modules > Please send all messages back to modules@perl.org with no CC to me. >
