[28189] in Perl-Users-Digest
Perl-Users Digest, Issue: 9553 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Aug 3 09:06:05 2006
Date: Thu, 3 Aug 2006 06:05:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Thu, 3 Aug 2006 Volume: 10 Number: 9553
Today's topics:
Re: Beginner: match /$key/ <rvtol+news@isolution.nl>
do not want to sort hash on key niraj.kumar.ait@gmail.com
Re: do not want to sort hash on key usenet@DavidFilmer.com
Re: do not want to sort hash on key <rvtol+news@isolution.nl>
Re: executing perl script without .pl extension tweaky@gmail.com
Re: foreach aliasing, my variables, and visibility in s <sgt19@tid.es>
Re: How probably not to hand over a variable from one p <youcontrol@hispeed.ch>
Re: How probably not to hand over a variable from one p <youcontrol@hispeed.ch>
Re: How probably not to hand over a variable from one p <1usa@llenroc.ude.invalid>
Re: How probably not to hand over a variable from one p <mritty@gmail.com>
Re: How probably not to hand over a variable from one p <youcontrol@hispeed.ch>
Re: How probably not to hand over a variable from one p <1usa@llenroc.ude.invalid>
Re: How probably not to hand over a variable from one p <mritty@gmail.com>
Re: How probably not to hand over a variable from one p <David.Squire@no.spam.from.here.au>
Re: how to "anonymize" Perl script before publishing it <nobody@dizum.com>
How to pass 2D array to sub function and return 2D arra <zhushenli@gmail.com>
Re: How to pass 2D array to sub function and return 2D <sisyphus1@nomail.afraid.org>
Re: How to pass 2D array to sub function and return 2D anno4000@radom.zrz.tu-berlin.de
Re: How to pass 2D array to sub function and return 2D <mritty@gmail.com>
Re: need perl dev in santa monica CA 100k+ f/t anno4000@radom.zrz.tu-berlin.de
Re: need perl dev in santa monica CA 100k+ f/t <jue@monster-berlin.de>
Re: perl editor anno4000@radom.zrz.tu-berlin.de
Re: perl_parse and multi threading <rprp@gmx.net>
Re: perl_parse and multi threading anno4000@radom.zrz.tu-berlin.de
Re: perl_parse and multi threading <rvtol+news@isolution.nl>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 3 Aug 2006 09:58:59 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Beginner: match /$key/
Message-Id: <eashj0.1f8.1@news.isolution.nl>
Marek Stepanek schreef:
> while (<DATA>)
> {
> chomp;
> last if /keyword/;
> push @lines1, $_;
> }
I would make that:
while (<DATA>)
{
last if /\bkeyword\b/;
chomp;
push @lines1, $_;
}
Or maybe you aimed for /^keyword$/ ?
$/ = "\nkeyword\n" ;
@lines1 = split /\n/, <DATA> ;
> my $start_day = "15";
> my $start_month = "07";
> my $year = "2006";
my ($year, $start_month, $start_day) = ('2006', '07', '15') ;
or just
my ($year, $start_month, $start_day) = (2006, 7, 15) ;
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: 3 Aug 2006 00:13:47 -0700
From: niraj.kumar.ait@gmail.com
Subject: do not want to sort hash on key
Message-Id: <1154589227.042058.271820@s13g2000cwa.googlegroups.com>
My hash automatically sort the data on key. I do not want to sort data
I just want to store the data in the way I store it.Is there any way
TIA
Niraj
------------------------------
Date: 3 Aug 2006 00:24:13 -0700
From: usenet@DavidFilmer.com
Subject: Re: do not want to sort hash on key
Message-Id: <1154589852.943034.31760@i42g2000cwa.googlegroups.com>
niraj.kumar.ait@gmail.com wrote:
> My hash automatically sort the data on key.
No it doesn't. If you observe this behavior, it's pure coincidence (and
it's probably a very small hash). Hashes are psuedo-random.
> I just want to store the data in the way I store it.Is there any way
Have you read the perl FAQ?
perldoc -q order
returns this relevant article:
How can I make my hash remember the order I put elements into it?
--
David Filmer (http://DavidFilmer.com)
------------------------------
Date: Thu, 3 Aug 2006 10:04:39 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: do not want to sort hash on key
Message-Id: <eashsd.1f8.1@news.isolution.nl>
niraj.kumar.ait@gmail.com schreef:
> My hash automatically sort the data on key.
It doesn't.
> I do not want to sort data
> I just want to store the data in the way I store it.
That's a FAQ:
perldoc -q hash.*order
> Is there any way
Use an array.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: 3 Aug 2006 05:58:58 -0700
From: tweaky@gmail.com
Subject: Re: executing perl script without .pl extension
Message-Id: <1154609938.148815.32740@m73g2000cwd.googlegroups.com>
I appreciate everyone's responses, and yes, in retrospect, this was the
incorrect group to post in, but the quoted response was completely
inappropriate. It was working last week, but like I alluded to, I can't
quite remember how I did it. I could be wrong, I may have been testing
under an AMPP setup and gotten it to work there, but in either case,
the response was simply not needed.
Matt Garrish wrote:
> I always enjoy the "I don't know what I'm talking about but I'll
> pretend it was working last week" approach to questions, though. : )
------------------------------
Date: Thu, 03 Aug 2006 09:08:43 +0200
From: Stephan Titard <sgt19@tid.es>
Subject: Re: foreach aliasing, my variables, and visibility in sub
Message-Id: <eas7ds$34k4@news.hi.inet>
Ben Morrow escribió:
> Quoth sgt19DELCAPS@tidNOSPAM.es:
>>> The abstract concepts may be orthogonal, but the Perl implementations
>>> certainly are not. The only useful way to get closures is with anonymous
>>> subs. (You can get closures with named subs by using string eval, but I
>>> think that oddity only qualifies as "slightly deviating from parallel"
>>> rather than being orthogonal.)
>>>
>>> Xho
>>>
>> actually having
>> make_sub {
>> my $subname = shift;
>> sub $subname { ...}
>> }
>> could be syntactic sugar for the glob thing
>>
>> make_sub {
>> my subname = shift;
>> no strict
>> *{$subname} = sub {...}
>> }
>
> That leads to different, just as weird behaviour. Now when you call
> &{$subname} you get the lexicals from the last time make_sub was called.
>
> The 'sub foo {...}' semantics differ from '*foo = sub {...}' in that
> (effectively) the first is only executed once. It's equivalent to
> 'BEGIN { *foo = sub {...} }'.
>
> Ben
>
this is a common way to make code templates (besides eval)
and getting the lexicals from the last time is actually what I expect;
an anonymous glob is used when you use sub '{...}' to hang the CV
and I alias it as soon as it is created
compare
my $sub = sub {...};
my *glob = \&$sub;
vs
*glob = sub {...};
Besides the fact it is not a useful closure do you see actually
something wrong in using that...I have been using this for years
without any negative side-effect so far...
--stephan
------------------------------
Date: Thu, 3 Aug 2006 12:42:16 +0200
From: =?ISO-8859-1?Q?Markus_H=E4nchen?= <youcontrol@hispeed.ch>
Subject: Re: How probably not to hand over a variable from one perl script to another
Message-Id: <44d1d305@news1.ethz.ch>
On 2006-08-02 23:13:36 +0200, "A. Sinan Unur" <1usa@llenroc.ude.invalid> said:
>
> Now, I don't see a good reason in this case for using temporary files.
> Why not pass the argument directly on the command line?
>
> system 'runit.pl', $variable;
Thanks a lot for your detailed advice, I'll try to digest it one by
one. Here is the bit I thought would help me most, unfortunately it
does not work (I guess because there is something I do not understand
here):
$variable = 1;
system 'runit.pl', $variable;
>>> pico runit.pl
#! /usr/bin/perl
print "$variable \n";
------------------------------
Date: Thu, 3 Aug 2006 14:06:56 +0200
From: =?ISO-8859-1?Q?Markus_H=E4nchen?= <youcontrol@hispeed.ch>
Subject: Re: How probably not to hand over a variable from one perl script to another
Message-Id: <44d1e6de@news1.ethz.ch>
> use...@DavidFilmer.com wrote:
>> Read up on how @ARGV works.
>
> Oops - meant to give you a reference:
>
> perldoc perlvar
Thanks for your advice, I have read that reference but it is way too
comprehensive. My only knowledge of Perl comes from reading the first
half of the book 'Learning Perl' by Phoenix and Schwartz.
I need simple examples (as I found them in the book), the original Perl
documentation is way too difficult for me in most cases.
I am coming from Matlab, there handing over a variable to another
script or function is done either by using it as an invocation argument
or by making the variable global.
I have the feeling that @ARGV might help me but I need an example of
how this is done, and an example which does not have other code in it
that I do not understand.
I know that what I call 'other code' might only be useful conventions
but in 'Learning Perl' one starts without these conventions, because
you first have to understand the basics before you comprehend why
conventions are useful and how they work.
------------------------------
Date: Thu, 03 Aug 2006 12:30:26 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: How probably not to hand over a variable from one perl script to another
Message-Id: <Xns981456A33A32asu1cornelledu@127.0.0.1>
Markus Hänchen <youcontrol@hispeed.ch> wrote in
news:44d1d305@news1.ethz.ch:
> On 2006-08-02 23:13:36 +0200, "A. Sinan Unur"
> <1usa@llenroc.ude.invalid> said:
>>
>> Now, I don't see a good reason in this case for using temporary
>> files. Why not pass the argument directly on the command line?
>>
>> system 'runit.pl', $variable;
>
> Thanks a lot for your detailed advice, I'll try to digest it one by
> one. Here is the bit I thought would help me most, unfortunately it
> does not work (I guess because there is something I do not understand
> here):
>
> $variable = 1;
> system 'runit.pl', $variable;
>
>>>> pico runit.pl
> #! /usr/bin/perl
> print "$variable \n";
#!/usr/bin/perl
use strict;
use warnings;
my ($variable) = @ARGV;
print "$variable\n";
__END__
A variable you declare in one program exists independently of variables in
other programs.
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)
comp.lang.perl.misc guidelines on the WWW:
http://augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: 3 Aug 2006 05:34:48 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: How probably not to hand over a variable from one perl script to another
Message-Id: <1154608488.736313.17290@h48g2000cwc.googlegroups.com>
Markus H=E4nchen wrote:
> On 2006-08-02 23:13:36 +0200, "A. Sinan Unur" <1usa@llenroc.ude.invalid> =
said:
> >
> > Now, I don't see a good reason in this case for using temporary files.
> > Why not pass the argument directly on the command line?
> >
> > system 'runit.pl', $variable;
>
> Thanks a lot for your detailed advice, I'll try to digest it one by
> one. Here is the bit I thought would help me most, unfortunately it
> does not work (I guess because there is something I do not understand
> here):
>
> $variable =3D 1;
> system 'runit.pl', $variable;
>
> >>> pico runit.pl
> #! /usr/bin/perl
> print "$variable \n";
First, put the lines:
use strict;
use warnings;
in every script you write. Right below the shebang. They will catch
90% of the errors you make - including this one.
@ARGV is the array that contains the arguments passed to your Perl
program. In this example, you ran the program runit.pl with an
argument of whatever was inside $variable. Therefore, @ARGV in
runit.pl contains exactly one element - whatever was in $variable when
runit.pl was called from the previous script.
Simplify things a little - make this one program, not two. Say you
have your program runit.pl. On the command line, you type:
./runit.pl foo 32 "hello world"
In that case, runit.pl's @ARGV will contain three elements: the string
'foo', the number 32, and the string 'hello world'.
If you were to type on your command line:
./runit.pl
then runit.pl's @ARGV would be empty.
Now, in your situation, you are using a separate program to call
runit.pl, rather than typing it on the command line. That's the only
difference. When you use the system() function, Perl executes the
program that you passed as system()'s first argument, passing that
program the remaining arguments.
Does that help to clarify at all?
Paul Lalli
------------------------------
Date: Thu, 3 Aug 2006 14:38:57 +0200
From: =?ISO-8859-1?Q?Markus_H=E4nchen?= <youcontrol@hispeed.ch>
Subject: Re: How probably not to hand over a variable from one perl script to another
Message-Id: <44d1ee5f@news1.ethz.ch>
>
> $variable = 5;
> system 'runit.pl', $variable;
>
>>>> pico runit.pl
> #! /usr/bin/perl
> print "$variable \n";
Thought, this might work instead:
#! /usr/bin/perl
$variable = @ARGV;
print "$variable \n";
But, helas, nope.
------------------------------
Date: Thu, 03 Aug 2006 12:51:42 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: How probably not to hand over a variable from one perl script to another
Message-Id: <Xns98145A3E8566Casu1cornelledu@127.0.0.1>
Markus Hänchen <youcontrol@hispeed.ch> wrote in
news:44d1ee5f@news1.ethz.ch:
>>
>> $variable = 5;
>> system 'runit.pl', $variable;
>>
>>>>> pico runit.pl
>> #! /usr/bin/perl
>> print "$variable \n";
>
> Thought, this might work instead:
>
> #! /usr/bin/perl
#!/usr/bin/perl
use strict;
use warnings;
> $variable = @ARGV;
> print "$variable \n";
>
> But, helas, nope.
ITYM, 'alas'.
my $variable = @ARGV;
evaluates @ARGV in scalar context (I recommend you read about scalar
versus list context).
As I mentioned before, when you find yourself being puzzled by these
issues, the best idea is to go back to your books for a while.
First, understand the basics of Perl. Then, learn about modules and
objects to see how you can divide a program into smaller chunks.
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)
comp.lang.perl.misc guidelines on the WWW:
http://augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: 3 Aug 2006 06:04:47 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: How probably not to hand over a variable from one perl script to another
Message-Id: <1154610286.999119.189510@s13g2000cwa.googlegroups.com>
Markus H=E4nchen wrote:
> >
> > $variable =3D 5;
> > system 'runit.pl', $variable;
> >
> >>>> pico runit.pl
> > #! /usr/bin/perl
> > print "$variable \n";
>
> Thought, this might work instead:
>
> #! /usr/bin/perl
> $variable =3D @ARGV;
> print "$variable \n";
This is known as "throwing it at the wall and seeing what sticks" and
is a very poor method of programming. Please go read a decent tutorial
on Perl. How to get one item out of an array is a very basic concept.
If you are a beginner, that's fine. We all were at one point. But you
must accept that you are a beginner, and *learn* the language, not just
type random lines of code until something works.
There are several good tutorials out there. I suggest you open your
console and type:
perldoc perlintro
followed by
perldoc perlsyn
and=20
perldoc perldata
Paul Lalli
------------------------------
Date: Thu, 03 Aug 2006 14:03:40 +0100
From: David Squire <David.Squire@no.spam.from.here.au>
Subject: Re: How probably not to hand over a variable from one perl script to another
Message-Id: <eass7c$k95$1@gemini.csx.cam.ac.uk>
Markus Hänchen wrote:
> I have the feeling that @ARGV might help me but I need an example of how
> this is done, and an example which does not have other code in it that I
> do not understand.
----test.pl----
#!/usr/bin/perl
use strict;
use warnings;
print $ARGV[0];
----
prompt>./test.pl 4.5
4.5
----
Note this is really a question about command line arguments, not passing
perl variables between perl scripts.
DS
------------------------------
Date: Thu, 3 Aug 2006 12:40:10 +0200 (CEST)
From: Nomen Nescio <nobody@dizum.com>
Subject: Re: how to "anonymize" Perl script before publishing it?
Message-Id: <5aade748b2d4c30d9e37128a76397fb6@dizum.com>
usenet@DavidFilmer.com wrote:
> Nomen Nescio wrote:
> > I want to publish a few of my Perl programs on usenet but I don't want
> > it to be obvious who wrote them.
>
> You can always use Acme::Bleach to 'clean up' your program:
> http://search.cpan.org/~dconway/Acme-Bleach-1.12/lib/Acme/Bleach.pm
Ha! I want the program which I'm donating to the public domain to be
readable and modifiable by other people.
------------------------------
Date: 3 Aug 2006 01:31:29 -0700
From: "Davy" <zhushenli@gmail.com>
Subject: How to pass 2D array to sub function and return 2D array?
Message-Id: <1154593889.794457.16810@m79g2000cwm.googlegroups.com>
Hi all,
I want to pass 2D array to sub function and return 2D array.
//--------------------------
For example,
use strict;
use warnings;
my @array=([1,2,3],[4,5,6],[7,8,9]);
my $array_ref = \@array;
$array_r = increase_array_element($array_ref);
sub increase_array_element {
//recover the 2D array
my @array_tmp = @{$array_ref};
print $array_tmp[2][2];
return \@array_tmp;
}
//-------------------------
But it seems the compile did not think @array_tmp is a 2D array?
Thanks!
Davy
------------------------------
Date: Thu, 3 Aug 2006 19:14:16 +1000
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: How to pass 2D array to sub function and return 2D array?
Message-Id: <44d1bf5b$0$22362$afc38c87@news.optusnet.com.au>
"Davy" <zhushenli@gmail.com> wrote in message
news:1154593889.794457.16810@m79g2000cwm.googlegroups.com...
> Hi all,
>
> I want to pass 2D array to sub function and return 2D array.
>
> //--------------------------
> For example,
> use strict;
> use warnings;
> my @array=([1,2,3],[4,5,6],[7,8,9]);
> my $array_ref = \@array;
>
> $array_r = increase_array_element($array_ref);
>
> sub increase_array_element {
> //recover the 2D array
> my @array_tmp = @{$array_ref};
> print $array_tmp[2][2];
> return \@array_tmp;
> }
> //-------------------------
>
> But it seems the compile did not think @array_tmp is a 2D array?
>
Best to copy'n'paste code. The code you have posted won't compile.
Just as inside the subroutine where you dereferenced the array reference
($array_ref) to an array (@array_temp), you could do the same with $array_r
(which is also an array reference - since that is what the subroutine
returns).
Something like:
use strict;
use warnings;
my @array=([1,2,3],[4,5,6],[7,8,9]);
my $array_ref = \@array;
my $array_r = increase_array_element($array_ref);
my @array_r_r = @{$array_r};
print $array_r_r[1][1], "\n";
sub increase_array_element {
my @array_tmp = @{$array_ref};
print $array_tmp[2][2], "\n";
return \@array_tmp;
}
Cheers,
Rob
------------------------------
Date: 3 Aug 2006 09:29:24 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: How to pass 2D array to sub function and return 2D array?
Message-Id: <4jdtvkF7i492U1@news.dfncis.de>
Davy <zhushenli@gmail.com> wrote in comp.lang.perl.misc:
> Hi all,
>
> I want to pass 2D array to sub function and return 2D array.
>
> //--------------------------
That's not a valid Perl comment. It's a fatal error.
> For example,
> use strict;
> use warnings;
> my @array=([1,2,3],[4,5,6],[7,8,9]);
> my $array_ref = \@array;
>
> $array_r = increase_array_element($array_ref);
$array_r is undeclared. That's a fatal error under "strict".
Calling "increase_array_ref" with an argument is useless because
the sub doesn't look at its arguments.
> sub increase_array_element {
> //recover the 2D array
> my @array_tmp = @{$array_ref};
> print $array_tmp[2][2];
> return \@array_tmp;
> }
> //-------------------------
See above.
> But it seems the compile did not think @array_tmp is a 2D array?
How do you know that?
Your code doesn't compile at all, you didn't even bother to run it
before posting.
Make your program runnable. If it still doesn't do what you expect,
post again, explaining what you expected and what happens instead.
Anno
------------------------------
Date: 3 Aug 2006 05:39:50 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: How to pass 2D array to sub function and return 2D array?
Message-Id: <1154608790.029895.97250@p79g2000cwp.googlegroups.com>
Sisyphus wrote:
> "Davy" <zhushenli@gmail.com> wrote in message
> news:1154593889.794457.16810@m79g2000cwm.googlegroups.com...
>
>
> Just as inside the subroutine where you dereferenced the array reference
> ($array_ref) to an array (@array_temp), you could do the same with $array_r
> (which is also an array reference - since that is what the subroutine
> returns).
>
> Something like:
>
> use strict;
> use warnings;
> my @array=([1,2,3],[4,5,6],[7,8,9]);
> my $array_ref = \@array;
>
> my $array_r = increase_array_element($array_ref);
> my @array_r_r = @{$array_r};
> print $array_r_r[1][1], "\n";
>
> sub increase_array_element {
> my @array_tmp = @{$array_ref};
> print $array_tmp[2][2], "\n";
> return \@array_tmp;
> }
This code contains the same error as the OP's. You are passing this
subroutine an argument, but never obtaining that argument from within
the subroutine. It will "work" simply because the argument you passed
was declared within the scope of both the function definition and the
function call, but that's not what you want to do.
sub increase_array_element {
my @array_temp = @{$_[0]};
$array_tmp[2][2]++;
print $array_tmp[2][2], "\n";
return \@array_tmp;
}
Please note that because of the way multi-dimensional structures work
in Perl, both the original and modified arrays contain references to
the *same* arrays, and so you have actually modified both $array_r and
$array_ref. . .
Paul Lalli
------------------------------
Date: 3 Aug 2006 11:39:12 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: need perl dev in santa monica CA 100k+ f/t
Message-Id: <4je5j0F7j4njU1@news.dfncis.de>
David H. Adler <dha@panix.com> wrote in comp.lang.perl.misc:
> On 2006-08-02, David Squire <David.Squire@no.spam.from.here.au> wrote:
> > usenet@DavidFilmer.com wrote:
> >> David H. Adler wrote:
> >>> Happens all the time. The weird thing is, although it happens all the
> >>> time, I have *never* come across anyone named Alder. :-)
> >>
> >> Lots of towns have streets named Alder,
> >
> >
> > Yep, but probably named after trees rather than people.
>
> Exactly.
...while the person is presumably named after a bird.
Anno
------------------------------
Date: 3 Aug 2006 05:36:42 -0700
From: "Thomas J." <jue@monster-berlin.de>
Subject: Re: need perl dev in santa monica CA 100k+ f/t
Message-Id: <1154608602.886639.219270@m73g2000cwd.googlegroups.com>
> > usenet@DavidFilmer.com wrote:
> >
> > Yep, but probably named after trees rather than people.
>
one more OT:
Adler is the german word for eagle
------------------------------
Date: 3 Aug 2006 12:08:37 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: perl editor
Message-Id: <4je7a5F7jduuU1@news.dfncis.de>
Abigail <abigail@abigail.be> wrote in comp.lang.perl.misc:
> Ted Zlatanov (tzz@lifelogs.com) wrote on MMMMDCCXIX September MCMXCIII in
> <URL:news:g69vepbjd1g.fsf@CN1374059D0130.kendall.corp.akamai.com>:
> <> On 2 Aug 2006, bik.mido@tiscalinet.it wrote:
> <>
> <> On 01 Aug 2006 20:17:20 GMT, Abigail <abigail@abigail.be> wrote:
> <> >
> <> >> vim isn't vi. Despite toy OS distro's firing up 'vim' is you type 'vi'.
> <> >
> <> > What should they do? Avoid it altogether? I don't use vi myself, but I
> <> > wouldn't regard it as such a bad thing...
> <>
> <> I think Abigail is referring to the original request for a "free"
> <> editor, which vi isn't but vim is.
> <>
> <> Plain vi is pretty awful, so it should probably be avoided altogether.
> <> I speak from experience, having used vi on Solaris for a while.
> <> Compared to vim it's simply outdated, and it has too many limitations
> <> to be useful for any serious programming. For Perl specifically,
> <> vim's support is much better.
>
>
> I do most of my Perl coding in 'vile', another 'vi' clone. However, over
> 99% of the commands I use would be identical in either 'vile' and 'vi'.
>
> I'd say that 'vi' is more than sufficient for coding Perl. Some of the
> extras of the 'vi' clones are nice to have, but I've yet to find a
> feature that's impossible to live without.
The one thing I miss when I don't have vim it is its QuickFix
feature. Together with Vi::QuickFix you can visit all places the
last Perl run has output errors or warnings, without copy/pasting
or retyping file names and line numbers. I can do without the delay
and load on short-term memory.
Anno
------------------------------
Date: Thu, 03 Aug 2006 09:10:05 +0200
From: Reinhard Pagitsch <rprp@gmx.net>
To: lililevy@hotmail.com
Subject: Re: perl_parse and multi threading
Message-Id: <44D1A14D.3080204@gmx.net>
Hello,
lililevy@hotmail.com wrote:
> Hello,
>
> I would very much appreciate your answers on the following issue.
> I have a multi threaded application. Each thread is running a function
> that creates a perl interpreter and uses it to parse and then run a
> perl function from an arbitrary file.
> After running this application for a while I'm having a deadlock and
> I can see that 10 threads are in the perl_parse function.
> I'm running on WInXP with perl 5.8.3.809.
> Are any of you are familiar with such a problem? Do you have an idea
> why this can happen?
>
Try to ask in perl.xs. I think they have more experience regarding this
issues.
regards,
Reinhard
------------------------------
Date: 3 Aug 2006 09:14:15 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: perl_parse and multi threading
Message-Id: <4jdt37F7jg1tU1@news.dfncis.de>
Reinhard Pagitsch <rpirpag@aon.at> wrote in comp.lang.perl.misc:
> Hello,
>
> lililevy@hotmail.com wrote:
> > Hello,
> >
> > I would very much appreciate your answers on the following issue.
> > I have a multi threaded application. Each thread is running a function
> > that creates a perl interpreter and uses it to parse and then run a
> > perl function from an arbitrary file.
> > After running this application for a while I'm having a deadlock and
> > I can see that 10 threads are in the perl_parse function.
> > I'm running on WInXP with perl 5.8.3.809.
> > Are any of you are familiar with such a problem? Do you have an idea
> > why this can happen?
> >
>
> Try to ask in perl.xs. I think they have more experience regarding this
> issues.
What is perl.xs? It's not a Usenet group.
Anno
------------------------------
Date: Thu, 3 Aug 2006 12:24:10 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: perl_parse and multi threading
Message-Id: <easpts.1ig.1@news.isolution.nl>
anno4000@radom.zrz.tu-berlin.de schreef:
> Reinhard Pagitsch:
>> lililevy:
>>> I would very much appreciate your answers on the following issue.
>>> I have a multi threaded application. Each thread is running a
>>> function that creates a perl interpreter and uses it to parse and
>>> then run a perl function from an arbitrary file.
>>> After running this application for a while I'm having a deadlock and
>>> I can see that 10 threads are in the perl_parse function.
>>> I'm running on WInXP with perl 5.8.3.809.
>>> Are any of you are familiar with such a problem? Do you have an idea
>>> why this can happen?
>>
>> Try to ask in perl.xs. I think they have more experience regarding
>> this issues.
>
> What is perl.xs? It's not a Usenet group.
You can find it as such at news://nntp.perl.org/perl.xs
and at several other mail2news-gateways.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 9553
***************************************
