[31085] in Perl-Users-Digest
Perl-Users Digest, Issue: 2330 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 10 14:09:49 2009
Date: Fri, 10 Apr 2009 11:09:14 -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 Fri, 10 Apr 2009 Volume: 11 Number: 2330
Today's topics:
Berkeley DB 4.7.25 "pthread_self", and feature request <liarafan@xs4all.nl>
Bioinformatics Suite <raghavagps@gmail.com>
Re: Bioinformatics Suite sln@netherlands.com
Re: calculate CDF google@edcallahan.com
Re: calculate CDF google@edcallahan.com
Re: calculate CDF <uri@stemsystems.com>
Re: calculate CDF sln@netherlands.com
Re: how to check missing breaks in switch case blocks sln@netherlands.com
Match Whole word only <Ansher.M@gmail.com>
Re: Match Whole word only <glex_no-spam@qwest-spam-no.invalid>
Re: Match Whole word only <klaus03@gmail.com>
Re: Match Whole word only <tadmc@seesig.invalid>
Re: Match Whole word only <someone@example.com>
Re: Match Whole word only sln@netherlands.com
Re: perl values for batch script to use sln@netherlands.com
Re: Pipe Between Programs <edgrsprj@ix.netcom.com>
Re: Pipe Between Programs <edgrsprj@ix.netcom.com>
Re: Pipe Between Programs <noreply@gunnar.cc>
Re: Pipe Between Programs <jurgenex@hotmail.com>
Re: Pipe Between Programs <tadmc@seesig.invalid>
Re: Pipe Between Programs <jurgenex@hotmail.com>
Re: Pipe Between Programs sln@netherlands.com
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 10 Apr 2009 19:59:16 +0200
From: "Mark" <liarafan@xs4all.nl>
Subject: Berkeley DB 4.7.25 "pthread_self", and feature request
Message-Id: <ha2dnU5ocaNoFULUnZ2dnUVZ8jednZ2d@giganews.com>
Hello all (and hoping Paul Marquess catches this too),
Yesterday I upgraded my entire server to Berkeley DB 4.7.25 -- a major
operation (what with recompiling everything against the new libs and all.
It seems very stable, so far, and Berkeley, the Perl module, is lightning
fast!
One thing, though, whilst compiling, I got an error about: "pthread_self"
being an undefined symbol. I subsequently removed the
--with-enable-pthread_api option from the Makefile, as I don't seem to
have the required libraries (this is a slightly older gcc 2.95.4 FreeBSD
compiler). Everything seems totally fine, now. So, do I really need the
"pthread_self" stuff? My guess is, I can do without. I ran several very
severe concurrency tests on de new DB 4.7, and they didn't give an inch,
which leads me to believe I'm probably fine. Am I?
As a feature request, for the BerkeleyDB module, when the shared ENV __db*
files get corrupted (this can happen; for instance, on a bad reboot of the
server, or hung process killed with -9), the BerkeleyDB module basically
just hangs when trying to reopen the environment, until such time I kill
the process trying to use it, and manually delete the __db* files first.
I wonder, could perhaps some sanity checks be done against the shared env?
Thanks,
- Mark
------------------------------
Date: Fri, 10 Apr 2009 10:39:22 -0700 (PDT)
From: Raghava <raghavagps@gmail.com>
Subject: Bioinformatics Suite
Message-Id: <d6c7a260-7ee0-46ad-8629-ae61fe88954d@f1g2000prb.googlegroups.com>
Dear Colleagues
As you know our group have developed number of webservers over the
years. I got lot of request related to i) availability of source
code; ii) perl scripts used to build software; iii) standalone
version of methods. In order to help our bioinformatics users
particularly young developers who wish to develop bioinformatics
programs; first time we are releasing source code (written in PERL)
for public. I hope these perl scripts will be useful for
bioinformatics community.
Codes are available from
http://www.imtech.res.in/raghava/gpsr/
https://sourceforge.net/projects/gpsraghava/
This is just starting, we will release all software to public in next
one year. I will appreciate you comment/suggestion/feedback on this
package GPSR.
Regards
Raghava
======================================================
# Dr G P S Raghava, Scientist and Head Bioinformatics Centre #
# Institute of Microbial Technology, Sector-39A, Chandigarh, India #
# Phone: +91-172-2690557, Fax: +91-172-2690632
#
# Eadd: http://www.imtech.res.in/raghava/ raghava@imtech.res.in #
#=====================================================
------------------------------
Date: Fri, 10 Apr 2009 10:47:09 -0700
From: sln@netherlands.com
Subject: Re: Bioinformatics Suite
Message-Id: <id1vt4tuino2kjgbbkp6cj0lns4esep18s@4ax.com>
On Fri, 10 Apr 2009 10:39:22 -0700 (PDT), Raghava <raghavagps@gmail.com> wrote:
>Dear Colleagues
>As you know our group have developed number of webservers over the
>years. I got lot of request related to i) availability of source
>code; ii) perl scripts used to build software; iii) standalone
>version of methods. In order to help our bioinformatics users
>particularly young developers who wish to develop bioinformatics
>programs; first time we are releasing source code (written in PERL)
>for public. I hope these perl scripts will be useful for
>bioinformatics community.
>
>Codes are available from
>http://www.imtech.res.in/raghava/gpsr/
>https://sourceforge.net/projects/gpsraghava/
>
>This is just starting, we will release all software to public in next
>one year. I will appreciate you comment/suggestion/feedback on this
>package GPSR.
>
>Regards
>
>Raghava
>======================================================
># Dr G P S Raghava, Scientist and Head Bioinformatics Centre #
># Institute of Microbial Technology, Sector-39A, Chandigarh, India #
># Phone: +91-172-2690557, Fax: +91-172-2690632
>#
># Eadd: http://www.imtech.res.in/raghava/ raghava@imtech.res.in #
>#=====================================================
Sure, my comment is your a pig researcher sucking down grants and getting
everybody to earn it for free.
-sln
------------------------------
Date: Fri, 10 Apr 2009 09:22:06 -0700 (PDT)
From: google@edcallahan.com
Subject: Re: calculate CDF
Message-Id: <c941ce80-1ed5-48bf-a6fe-6535de4eff5d@f19g2000yqo.googlegroups.com>
On Apr 8, 9:37=A0am, Tad J McClellan <ta...@seesig.invalid> wrote:
> What happened when you typed
>
> =A0 =A0 cumulative distribution function
>
> into the little box at:
>
> =A0 =A0http://search.cpan.org/
>
> ??
>
> --
> Tad McClellan
> email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
It's been a long time since I've looked around in this forum, nice to
know little has changed. If we deleted all the RTFM posts we'd cut the
size of the group in half :-) I've always understood why one might
not choose to help a person, but to take the time to make sure he
knows you won't help has always seemed strange.
------------------------------
Date: Fri, 10 Apr 2009 09:27:17 -0700 (PDT)
From: google@edcallahan.com
Subject: Re: calculate CDF
Message-Id: <fd57bb17-5e12-46b3-b778-62c77ce612e8@o11g2000yql.googlegroups.com>
On Apr 8, 10:49=A0am, "friend...@gmail.com" <hirenshah...@gmail.com>
wrote:
>
> In Math::CDF
>
> function: =A0pnorm($x)
>
> what is $x? how can I get value of $x.- Hide quoted text -
>
> - Show quoted text -
Math::CDF is a mathematical beast, not statistical, although is does
process formulas used in statistics. If you know the cummunulative
distribution function you are interested in, and it's included in the
module, then you can get the probability from the quantile ($x) or the
quantile from the probability. But as another poster said, the module
doesn't process raw data.
Honestly, if the manual at http://search.cpan.org/dist/Math-CDF/CDF.pm
doesn't make sense to you this is probably not the module you need to
be using for your problem.
------------------------------
Date: Fri, 10 Apr 2009 12:30:43 -0400
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: calculate CDF
Message-Id: <x7ws9swjws.fsf@mail.sysarch.com>
>>>>> "g" == google <google@edcallahan.com> writes:
g> Honestly, if the manual at http://search.cpan.org/dist/Math-CDF/CDF.pm
g> doesn't make sense to you this is probably not the module you need to
g> be using for your problem.
and if that isn't a case of RTFM, then i don't know what RTFM means.
pot meet kettle.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Free Perl Training --- http://perlhunter.com/college.html ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Fri, 10 Apr 2009 09:54:52 -0700
From: sln@netherlands.com
Subject: Re: calculate CDF
Message-Id: <jbuut49ti1i74u07ocitatka2j511mbo4e@4ax.com>
On Fri, 10 Apr 2009 09:22:06 -0700 (PDT), google@edcallahan.com wrote:
>On Apr 8, 9:37 am, Tad J McClellan <ta...@seesig.invalid> wrote:
>> What happened when you typed
>>
>> cumulative distribution function
>>
>> into the little box at:
>>
>> http://search.cpan.org/
>>
>> ??
>>
>> --
>> Tad McClellan
>> email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
>
>It's been a long time since I've looked around in this forum, nice to
>know little has changed. If we deleted all the RTFM posts we'd cut the
>size of the group in half :-) I've always understood why one might
>not choose to help a person, but to take the time to make sure he
>knows you won't help has always seemed strange.
Thats just nested. The next level is RTFM about this forum.
-sln
------------------------------
Date: Fri, 10 Apr 2009 10:00:11 -0700
From: sln@netherlands.com
Subject: Re: how to check missing breaks in switch case blocks
Message-Id: <iiuut4952f9r8pkpilb8i17jseoiobl5ms@4ax.com>
On Wed, 8 Apr 2009 19:53:39 -0700 (PDT), kernus <kernus@gmail.com> wrote:
>I want to know how to do a static code analysis with my C code in
>Perl, instead of splint.
>
>anyone give and ideas or some perl scripts?
>
>thanks in advance.
You know, that phrase 'code analysis' reminds me of the phrase
'engine repair'. I guess in both cases, a lot has to be taken apart
first.
By the time you develop a C/C++ parser in Perl, I have a feeling
you won't be asking that question.
-sln
------------------------------
Date: Fri, 10 Apr 2009 07:46:18 -0700 (PDT)
From: perl Newbie <Ansher.M@gmail.com>
Subject: Match Whole word only
Message-Id: <7f9a1b7e-712d-4ae1-ad8e-13963d132bed@k2g2000yql.googlegroups.com>
Hello ,
I am having trouble how to "match whole word only", the script I am
using here is
use warnings;
use strict;
my @lines=(
"l qa1;c=c(a0)'1'.or.c(a10)'2';&sort;&nz",
"n01 blah ... ;c=c(a9)'1'.and.c(a07)'1'",
"n01 blah ... ;c=c(a08)'1'.and.c(a11)'1'",
"*include q1.qin;kod=a05;axm=q4a4",
"*include q2.qin;pod=a06"
) ;
my @aval;
foreach my $l (@lines){
print "$l\n";
}
print "\n\n";
foreach my $l (@lines){
if ($l =~/a[0-9]+/) {
##print "$l\n";
my (@push_txt) = $l=~/(a[0-9]+)/g;
push @aval,@push_txt;
}
}
print "@aval\n";
With this I am getting all the values that qualifies condition a[0-9]+
including a1 from qa1 & a4 from q4a4.
How can I get match whole word values, in this case it should outputs
values a0 a10 a9 a07 a08 a11 a05 a06.
------------------------------
Date: Fri, 10 Apr 2009 10:07:37 -0500
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: Match Whole word only
Message-Id: <49df60b9$0$87069$815e3792@news.qwest.net>
perl Newbie wrote:
> Hello ,
>
> I am having trouble how to "match whole word only", the script I am
> using here is
>
> use warnings;
> use strict;
>
> my @lines=(
> "l qa1;c=c(a0)'1'.or.c(a10)'2';&sort;&nz",
> "n01 blah ... ;c=c(a9)'1'.and.c(a07)'1'",
> "n01 blah ... ;c=c(a08)'1'.and.c(a11)'1'",
> "*include q1.qin;kod=a05;axm=q4a4",
> "*include q2.qin;pod=a06"
> ) ;
>
>
> my @aval;
> foreach my $l (@lines){
> print "$l\n";
> }
>
> print "\n\n";
>
> foreach my $l (@lines){
> if ($l =~/a[0-9]+/) {
> ##print "$l\n";
> my (@push_txt) = $l=~/(a[0-9]+)/g;
> push @aval,@push_txt;
> }
> }
>
> print "@aval\n";
>
> With this I am getting all the values that qualifies condition a[0-9]+
> including a1 from qa1 & a4 from q4a4.
>
> How can I get match whole word values, in this case it should outputs
> values a0 a10 a9 a07 a08 a11 a05 a06.
>
>
if ($l =~/\ba[0-9]+/) {
##print "$l\n";
my (@push_txt) = $l=~/\b(a[0-9]+)/g;
push @aval,@push_txt;
}
To find out more, see: perldoc perlre
------------------------------
Date: Fri, 10 Apr 2009 08:09:50 -0700 (PDT)
From: Klaus <klaus03@gmail.com>
Subject: Re: Match Whole word only
Message-Id: <e7a5bef1-154c-4abd-9de5-2faa0f6a94a7@m24g2000vbp.googlegroups.com>
On Apr 10, 4:46=A0pm, perl Newbie <Anshe...@gmail.com> wrote:
> Hello ,
>
> I am having trouble how to "match whole word only", the script I am
> using here is
>
> use warnings;
> use strict;
>
> my @lines=3D(
> "l qa1;c=3Dc(a0)'1'.or.c(a10)'2';&sort;&nz",
> "n01 blah ... ;c=3Dc(a9)'1'.and.c(a07)'1'",
> "n01 blah ... ;c=3Dc(a08)'1'.and.c(a11)'1'",
> "*include q1.qin;kod=3Da05;axm=3Dq4a4",
> "*include q2.qin;pod=3Da06"
> ) ;
>
> my @aval;
> foreach my $l (@lines){
> =A0 =A0 =A0 =A0 print "$l\n";
>
> }
>
> print "\n\n";
>
> foreach my $l (@lines){
> =A0 =A0 =A0 =A0 if ($l =3D~/a[0-9]+/) {
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ##print "$l\n";
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 my (@push_txt) =3D $l=3D~/(a[0-9]+)/g;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 push @aval,@push_txt;
> =A0 =A0 =A0 =A0 }
>
> }
>
> print "@aval\n";
>
> With this I am getting all the values that qualifies condition a[0-9]+
> including a1 from qa1 & a4 from q4a4.
>
> How can I get match whole word values, in this case it should outputs
> values a0 a10 a9 a07 a08 a11 a05 a06.
try \b in your regular expression:
my (@push_txt) =3D $l=3D~/\b(a[0-9]+)\b/g;
--
Klaus
------------------------------
Date: Fri, 10 Apr 2009 10:11:17 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: Match Whole word only
Message-Id: <slrngtuocl.gfg.tadmc@tadmc30.sbcglobal.net>
perl Newbie <Ansher.M@gmail.com> wrote:
> I am having trouble how to "match whole word only",
> foreach my $l (@lines){
> if ($l =~/a[0-9]+/) {
> ##print "$l\n";
> my (@push_txt) = $l=~/(a[0-9]+)/g;
> push @aval,@push_txt;
> }
> }
foreach my $l (@lines){
push @aval, $l =~ /\b(a[0-9]+)\b/g;
}
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Fri, 10 Apr 2009 10:14:04 -0700
From: "John W. Krahn" <someone@example.com>
Subject: Re: Match Whole word only
Message-Id: <w7LDl.32207$0%2.27184@newsfe22.iad>
perl Newbie wrote:
>
> I am having trouble how to "match whole word only", the script I am
> using here is
>
> use warnings;
> use strict;
>
> my @lines=(
> "l qa1;c=c(a0)'1'.or.c(a10)'2';&sort;&nz",
> "n01 blah ... ;c=c(a9)'1'.and.c(a07)'1'",
> "n01 blah ... ;c=c(a08)'1'.and.c(a11)'1'",
> "*include q1.qin;kod=a05;axm=q4a4",
> "*include q2.qin;pod=a06"
> ) ;
>
>
> my @aval;
> foreach my $l (@lines){
> print "$l\n";
> }
>
> print "\n\n";
>
> foreach my $l (@lines){
> if ($l =~/a[0-9]+/) {
> ##print "$l\n";
> my (@push_txt) = $l=~/(a[0-9]+)/g;
> push @aval,@push_txt;
> }
> }
>
> print "@aval\n";
>
> With this I am getting all the values that qualifies condition a[0-9]+
> including a1 from qa1 & a4 from q4a4.
>
> How can I get match whole word values, in this case it should outputs
> values a0 a10 a9 a07 a08 a11 a05 a06.
$ perl -le'
my @lines = (
"l qa1;c=c(a0)\0471\047.or.c(a10)\0472\047;&sort;&nz",
"n01 blah ... ;c=c(a9)\0471\047.and.c(a07)\0471\047",
"n01 blah ... ;c=c(a08)\0471\047.and.c(a11)\0471\047",
"*include q1.qin;kod=a05;axm=q4a4",
"*include q2.qin;pod=a06",
);
foreach my $l ( @lines ) {
print $l;
}
my @aval = "@lines" =~ /\ba[0-9]+\b/g;
print "\n@aval\n";
'
l qa1;c=c(a0)'1'.or.c(a10)'2';&sort;&nz
n01 blah ... ;c=c(a9)'1'.and.c(a07)'1'
n01 blah ... ;c=c(a08)'1'.and.c(a11)'1'
*include q1.qin;kod=a05;axm=q4a4
*include q2.qin;pod=a06
a0 a10 a9 a07 a08 a11 a05 a06
John
--
Those people who think they know everything are a great
annoyance to those of us who do. -- Isaac Asimov
------------------------------
Date: Fri, 10 Apr 2009 10:34:54 -0700
From: sln@netherlands.com
Subject: Re: Match Whole word only
Message-Id: <cm0vt41u0v4phfktp6bfj512ls42e1hmgn@4ax.com>
On Fri, 10 Apr 2009 10:14:04 -0700, "John W. Krahn" <someone@example.com> wrote:
>perl Newbie wrote:
>>
>> I am having trouble how to "match whole word only", the script I am
>> using here is
>>
>> use warnings;
>> use strict;
>>
>> my @lines=(
>> "l qa1;c=c(a0)'1'.or.c(a10)'2';&sort;&nz",
>> "n01 blah ... ;c=c(a9)'1'.and.c(a07)'1'",
>> "n01 blah ... ;c=c(a08)'1'.and.c(a11)'1'",
>> "*include q1.qin;kod=a05;axm=q4a4",
>> "*include q2.qin;pod=a06"
>> ) ;
>>
>>
>> my @aval;
>> foreach my $l (@lines){
>> print "$l\n";
>> }
>>
>> print "\n\n";
>>
>> foreach my $l (@lines){
>> if ($l =~/a[0-9]+/) {
>> ##print "$l\n";
>> my (@push_txt) = $l=~/(a[0-9]+)/g;
>> push @aval,@push_txt;
>> }
>> }
>>
>> print "@aval\n";
>>
>> With this I am getting all the values that qualifies condition a[0-9]+
>> including a1 from qa1 & a4 from q4a4.
>>
>> How can I get match whole word values, in this case it should outputs
>> values a0 a10 a9 a07 a08 a11 a05 a06.
>
>$ perl -le'
>my @lines = (
> "l qa1;c=c(a0)\0471\047.or.c(a10)\0472\047;&sort;&nz",
> "n01 blah ... ;c=c(a9)\0471\047.and.c(a07)\0471\047",
> "n01 blah ... ;c=c(a08)\0471\047.and.c(a11)\0471\047",
> "*include q1.qin;kod=a05;axm=q4a4",
> "*include q2.qin;pod=a06",
> );
>
>foreach my $l ( @lines ) {
> print $l;
>}
>
>my @aval = "@lines" =~ /\ba[0-9]+\b/g;
>
>print "\n@aval\n";
>'
>l qa1;c=c(a0)'1'.or.c(a10)'2';&sort;&nz
>n01 blah ... ;c=c(a9)'1'.and.c(a07)'1'
>n01 blah ... ;c=c(a08)'1'.and.c(a11)'1'
>*include q1.qin;kod=a05;axm=q4a4
>*include q2.qin;pod=a06
>
>a0 a10 a9 a07 a08 a11 a05 a06
>
>
>
>
>John
print
"l qa1;c=c(a0)\0471\047.or.c(a10)\0472\047;&sort;&nz
n01 blah ... ;c=c(a9)\0471\047.and.c(a07)\0471\047
n01 blah ... ;c=c(a08)\0471\047.and.c(a11)\0471\047
*include q1.qin;kod=a05;axm=q4a4
*include q2.qin;pod=a06
" =~ /\ba[0-9]+\b/g;
c:\temp>perl ee.pl
a0a10a9a07a08a11a05a06
c:\temp>
------------------------------
Date: Fri, 10 Apr 2009 09:39:06 -0700
From: sln@netherlands.com
Subject: Re: perl values for batch script to use
Message-Id: <ebtut4da439tpmqsuupk489qqqrui6l0f5@4ax.com>
On Wed, 8 Apr 2009 06:52:25 -0700 (PDT), Ron Bergin <rkb@i.frys.com> wrote:
>On Apr 7, 3:50 pm, s...@netherlands.com wrote:
>> On Tue, 7 Apr 2009 14:09:10 -0700 (PDT), Ron Bergin <r...@i.frys.com> wrote:
>> >On Apr 7, 10:58 am, Slickuser <slick.us...@gmail.com> wrote:
>> >> I have a filename (file.txt)
>>
>> >> file.txt contains:
>> >> Sample4.1.2009_US
>> >> Sample4.2.2009_ASIA
>>
>> >> I can parse this file in Perl fine. Now I want this value to be
>> >> available to use in a batch script.
>> >> I try using "set" but the info get clear once I exit perl script.
>>
>> >> perl_script.pl
>> >> open file.txt
>> >> parse info
>> >> use system to execute command ("set xxyz_US=Sample4.1.2009_US")
>> >> ("set xxyz_ASIA=Sample4.2.2009_ASIA")
>>
>> >Use setenv instead of the set command.
>>
>> >http://barnyard.syr.edu/~vefatica/#SETENV
>>
>> >Or, you could use the standard set command and then use Win32::API to
>> >call 2 C functions (RegFlushKey and BroadcastSystemMessage) to force
>> >that setting to be retained after the perl script ends, which is
>> >basically what setenv does.
>>
>> I don't understand posters taken verbatim. The dumb shmuks here
>> think a perl script can realistically shine shoes if asked. Literally.
>>
>> -sln
>
>
>I don't understand how your comment applies to mine. What you're
>trying to convey?
Well Ron I guess I'm saying "Some little programs for Windows NT/Intel" isn't
relative in environments for a long time now. No longer are apps cluttering up
the environment. Maybe your just a little behind the times.
-sln
------------------------------
Date: Fri, 10 Apr 2009 04:15:24 -0500
From: "E.D.G." <edgrsprj@ix.netcom.com>
Subject: Re: Pipe Between Programs
Message-Id: <PYudnWdxKfO9k0LUnZ2dnUVZ_tKdnZ2d@earthlink.com>
"Tad J McClellan" <tadmc@seesig.invalid> wrote in message
news:slrngts52q.2fj.tadmc@tadmc30.sbcglobal.net...
Thanks for the responses.
The main Perl language program that has been discussed here is already
running and has been available to researchers around the world since early
in March, 2009. The code that was posted in the first note does actually
start the Gnuplot graphics program running. And it does a good job of
somehow sending Gnuplot information and controlling its operation.
Previously that had to be done through file sharing. That process worked,
but not very well.
The "pipe" feature and other features being discussed are for updates and
for other programs being developed. I am going to have to do more reading to
understand the information regarding pipes. It is too inefficient and takes
too long to have detailed technical discussions regarding subjects like that
in Newsgroup notes. If there is anyone interested in discussing that pipe
technology then they should contact me by E-mail.
Thanks again.
------------------------------
Date: Fri, 10 Apr 2009 04:20:47 -0500
From: "E.D.G." <edgrsprj@ix.netcom.com>
Subject: Re: Pipe Between Programs
Message-Id: <nd6dnRjmp9T-kkLUnZ2dnUVZ_gadnZ2d@earthlink.com>
"TheGist" <thegist@nospam.net> wrote in message
news:grmf5a$52q$1@aioe.org...
The main project that has been discussed here is believed to involve
interactions between electromagnetic energy fields and earthquake fault
zones. Computer programs are being used to study those interactions and make
use of them to forecast earthquakes.
This is partly research. But it is mainly a disaster mitigation project.
Governments are being invited to and encouraged to use the technology.
------------------------------
Date: Fri, 10 Apr 2009 13:20:18 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Pipe Between Programs
Message-Id: <748obtF123l2lU1@mid.individual.net>
E.D.G. wrote:
> I am going to have to do more reading to understand the information
> regarding pipes.
Ok.
> It is too inefficient and takes too long to have detailed technical
> discussions regarding subjects like that in Newsgroup notes.
Not at all. This is a technical newsgroup, and detailed technical
discussions is what many (most?) threads here are about. But people
asking questions need to provide proper bases for discussion.
Besides reading up on pipes, I suggest that you also read the posting
guidelines for this group:
http://www.rehabitation.com/clpmisc/clpmisc_guidelines.html
> If there is anyone interested in discussing that pipe technology then
> they should contact me by E-mail.
Don't be surprised if nobody does. People here read clpmisc, and reply
to clpmisc.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 10 Apr 2009 05:13:31 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Pipe Between Programs
Message-Id: <epdut4500nnlpn8e7cviedd69e669bdl58@4ax.com>
"E.D.G." <edgrsprj@ix.netcom.com> wrote:
>"TheGist" <thegist@nospam.net> wrote in message
>news:grmf5a$52q$1@aioe.org...
>
>The main project that has been discussed here is believed to involve
>interactions between electromagnetic energy fields and earthquake fault
>zones. Computer programs are being used to study those interactions and make
>use of them to forecast earthquakes.
Your writing style looked familar and I did have a feeling I recognized
the kind of question. You had to get yet another identity to bypass all
those kill files, didn't you?
Back you go where you belong!
*PLONK*
jue
------------------------------
Date: Fri, 10 Apr 2009 08:38:39 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: Pipe Between Programs
Message-Id: <slrngtuiuv.fes.tadmc@tadmc30.sbcglobal.net>
Jürgen Exner <jurgenex@hotmail.com> wrote:
> "E.D.G." <edgrsprj@ix.netcom.com> wrote:
> You had to get yet another identity to bypass all
> those kill files, didn't you?
He's been using that same address for at least 5 years.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Fri, 10 Apr 2009 09:52:31 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Pipe Between Programs
Message-Id: <97uut4lkh4reum9arn9plsibah3fr635gc@4ax.com>
Tad J McClellan <tadmc@seesig.invalid> wrote:
>Jürgen Exner <jurgenex@hotmail.com> wrote:
>> "E.D.G." <edgrsprj@ix.netcom.com> wrote:
>
>> You had to get yet another identity to bypass all
>> those kill files, didn't you?
>
>He's been using that same address for at least 5 years.
Really? Well, ok, my appologies on that part.
I will investigate, why his posts started showing up again.
jue
------------------------------
Date: Fri, 10 Apr 2009 10:12:02 -0700
From: sln@netherlands.com
Subject: Re: Pipe Between Programs
Message-Id: <m4vut412s0vv3n7ueg3s6d7fcvm179bdoh@4ax.com>
On Thu, 9 Apr 2009 08:55:53 -0500, "E.D.G." <edgrsprj@ix.netcom.com> wrote:
>"RedGrittyBrick" <RedGrittyBrick@spamweary.invalid> wrote in message
>news:49dde077$0$26448$da0feed9@news.zen.co.uk...
>> E.D.G. wrote:
>
>Your answers are appreciated. But they are beyond my level of programming
>skills. As I said in the other post, I did look over the Perl documentation
>but did not understand the information.
>
>These projects all involve volunteer work. There is no funding available to
>hire professional computer programmers to do a better job. However, I am
>trying to get governments around the world to take over the work on at least
>one of the projects.
>
>I will go over the information a few more times. And if it still cannot be
>understood then researchers involved with these efforts will just have their
>programs exchange data through data files. They know less than I do about
>computer programming. At least that Gnuplot graphics program control code
>works and makes things a lot easier.
>
>That URL you listed is actually quite helpful. I was fairly sure there were
>Newsgroup archives out there somewhere. The main project being discussed in
>notes going back a decade in time is now fully operational and as of early
>March, 2009 became available as a freeware downloadable computer program.
Flowery language is no substitute for intelligence in technical matters.
Its just lipstick on a pig. Eventually the underlying motive becomes obvious,
to get somone to do work for you for free, for the glory of mankind, or some
such drivel spam.
-sln
------------------------------
Date: Fri, 10 Apr 2009 07:11:27 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <ziCDl.23026$c45.19040@nlpi065.nbdc.sbc.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
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 V11 Issue 2330
***************************************
