On Tue, 27 Jun 2006, Smith, Derek wrote:
So could this `$SIG{'PIPE'}="IGNORE";' be considered a global similar to
$ENV{"PATH"} = qq(/opt/SUNWsamfs/sbin:/usr/bin);
Yes, %SIG is a global hash.
Jorge
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
-Original Message-
From: Jorge Almeida [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 27, 2006 9:37 AM
To: John W. Krahn
Cc: Perl Beginners
Subject: Re: eval problem
On Tue, 27 Jun 2006, John W. Krahn wrote:
> Jorge Almeida wrote:
>> What is happening?
>
> When find
On Tue, 27 Jun 2006, John W. Krahn wrote:
Jorge Almeida wrote:
What is happening?
When find dies a SIGPIPE signal is sent to the parent process which kills it.
Thank you. Putting `$SIG{'PIPE'}="IGNORE";' in the beginning of my
program solves my problem.
Jorge
--
To unsubscribe, e-mail
Jorge Almeida wrote:
> Can someone help me to understand what's wrong with this? (Or: what I
> didn't understand about eval?)
>
> $ perl -e 'use strict;use warnings;eval{open(OUT,"|file")};eval{print
> OUT "aa\n";};eval{close OUT};;'
> Usage: file [-bcikLnNsvz] [-f namefile] [-F separator] [-m mag
--SNIP--
> Personally, I don't want to put a lid on any discussion. I think the
> characteristic which distinguishes this list as a beginners' list is not
> the level of the *response*, but rather the willingness of the respondants
> to address any *question*.
>
> Thanks,
> Nelson
And to do so i
In a message dated Tue, 2 Oct 2001 6:03:06 PM Eastern Daylight Time, Curtis Poe
<[EMAIL PROTECTED]> writes:
> Mea Culpa.
>
> While I do have some reservations about how prototypes were used in a particular
>example, I'll try
> to be more sensitive about the "beginners" aspect of things.
Curt
On Wed, Oct 03, 2001 at 11:01:48AM +0530, [EMAIL PROTECTED] wrote:
> so my earlier effort was basically to find out how we can capture the
> output of "eval($temp)" into a Perl variable, ...this variable could later
> be taken from the Perl stack ,converted into a C string and sent through
> the p
Hi everybody,
Thanks for sending the reply , but I think the problem is misunderstood
..thanks to the stupid way I which I put forward my problem!!
this is our case
we are trying to develop a Command line Interface for a simulator , the
requirements are that
the CLI as to be writ
At 03:23 PM 10/02/2001 -0700, Michael Kelly wrote:
>Well, being somewhat of a beginner myself, I think it is very helpful to
>look at stuff that's above your head. I certainly don't mind the fact that
>80% of the stuff on this list is above me, and I think that, when I do start
>dealing with some
> While this is true, it's seldom clear to the beginner when this list has
> diverted to esoterica. It's *critical* for a beginner to know what they
> *don't* need to pay attention to at the beginning, and we do them a
> disservice by commingling easy and not-so-easy stuff.
>
> So I'd back Zande
--- Zander Collier <[EMAIL PROTECTED]> wrote:
> With all due respect, if you're going to discuss the minutae,
> nuances, and other "advanced" Perl stuff, could you please do
> so on another list?
>
> This is [EMAIL PROTECTED]
Mea Culpa.
While I do have some reservations about how prototypes wer
At 05:56 PM 10/2/01 -0400, Brett W. McCoy wrote:
>On Wed, 3 Oct 2001, Zander Collier wrote:
>
> > With all due respect, if you're going to discuss the minutae,
> > nuances, and other "advanced" Perl stuff, could you please do
> > so on another list?
>
>I'm inclined to agree... however, I think it
On Wed, 3 Oct 2001, Zander Collier wrote:
> With all due respect, if you're going to discuss the minutae,
> nuances, and other "advanced" Perl stuff, could you please do
> so on another list?
I'm inclined to agree... however, I think it is helpful for beginners also
to be amongst more advanced c
With all due respect, if you're going to discuss the minutae,
nuances, and other "advanced" Perl stuff, could you please do
so on another list?
This is [EMAIL PROTECTED]
Publicly arguing this sort of thing on this list, at least to
me, makes it more intimidating to post what will be my silly
neo
> One of the problems with prototypes is that they are not prototypes, at
> least not in the sense that other programming languages use them.
I am aware of this "problem", which, personally, I don't consider a problem,
because it is documented fairly clearly.
> Instead, they allow us, amongt o
--- Michael Fowler <[EMAIL PROTECTED]> wrote:
> You could also make your own print function that appends to the variable of
> your choice:
>
> sub append_and_print (\$@) {
> my($var_ref, @stuff_to_print) = @_;
>
> $$var_ref = '' unless defined($$var_ref);
> my $sep =
On Mon, Oct 01, 2001 at 07:46:24PM +0530, [EMAIL PROTECTED] wrote:
> Instead of this behaviour of eval, Can I get what I want .i.e.. Can I
> capture the output in some variable. Like here I am printing "hi" on
> stdout. But I want this "hi" to be stored in some variable also.
So you want to store
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 01 October 2001 15:16
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: eval problem
>
>
>
>
> Hi everybody,
>
> I am facing a little problem with eval in perl.
>
> say I do the following:
18 matches
Mail list logo
