[30287] in Perl-Users-Digest
Perl-Users Digest, Issue: 1530 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat May 10 21:09:44 2008
Date: Sat, 10 May 2008 18:09:11 -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 Sat, 10 May 2008 Volume: 11 Number: 1530
Today's topics:
Re: DROP TABLE customers <jurgenex@hotmail.com>
Re: DROP TABLE customers <uri@stemsystems.com>
Re: DROP TABLE customers <get@bentsys.com>
FAQ 3.31 == FAQ 3.30 <jo@nosp.invalid>
Re: Get variable from its name string or vice versa? <hjp-usenet2@hjp.at>
Re: I need to extract an array from a scalar regex-wise <uri@stemsystems.com>
Re: I need to extract an array from a scalar regex-wise <get@bentsys.com>
Re: implementation for Parsing Expression Grammar? <see@sig.below>
Re: Perl DBI Module: SQL query where there is space in <m@rtij.nl.invlalid>
Re: Perl DBI Module: SQL query where there is space in <m@rtij.nl.invlalid>
Printing a new line kronecker@yahoo.co.uk
Re: Printing a new line (Jens Thoms Toerring)
Re: Printing a new line <jurgenex@hotmail.com>
Re: Printing a new line <ben@morrow.me.uk>
Re: Printing a new line <1usa@llenroc.ude.invalid>
Re: regex problem unresolved <jurgenex@hotmail.com>
Re: regex problem unresolved <benkasminbullock@gmail.com>
Re: The Importance of Terminology's Quality <lew@lewscanon.com>
Re: The Importance of Terminology's Quality <gneuner2/@/comcast.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 10 May 2008 20:31:10 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: DROP TABLE customers
Message-Id: <8b1c2413jg2b03avo3etutnk4al032n77n@4ax.com>
"Gordon Etly" <get@bentsys.com> wrote:
>Uri Guttman wrote:
>> Gordon Etly <get@bentsys.com> writes:
>> > A. Sinan Unur wrote:
>> > > Ignoramus26246 <ignoramus26246@NOSPAM.26246.invalid> wrote
>> > > in news:ZOGdnYzvPOYa9LnVnZ2dnUVZ_g-dnZ2d@giganews.com:
>
>> > > Back to the killfile you go with this self congratulatory
>> > > troll-bait >> drivel and your morphing personality.
>
>> > The world doesn't need to know who is going in your killfile. Please
>> > keep your private matters to yourself.
>Why is everything you don't like a "flame" to you? It was a basic
>comment, that one doesn't need to shout out to the world, "hey I'm going
>to ignore this guy!!!!!!". It's like standing in a busy terminal and
>yelling around that you're ignoring someone.
***PLONK***
jue
------------------------------
Date: Sat, 10 May 2008 21:08:45 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: DROP TABLE customers
Message-Id: <x7tzh5rhnn.fsf@mail.sysarch.com>
>>>>> "GE" == Gordon Etly <get@bentsys.com> writes:
GE> Uri Guttman wrote:
>> will you ever make a comment about perl code itself?
GE> It's not a requirement to comment. It's certainally no concern of yours,
GE> as you are not mine nor anyone else's keeper.
it is a concern of this group. all you ever comment about is how others
post things. this means you are not contributing anything useful. those
who post about perl will also comment about other stuff. since you don't
mention any perl code ever, you have no right to post about others. the
rule as has been told to you is those who help with perl can make other
comments.
>> you are the most meta flamer i have seen in a while. even
>> moronzilla talked about perl itself more often than you.
GE> Why is everything you don't like a "flame" to you? It was a basic
GE> comment, that one doesn't need to shout out to the world, "hey I'm
GE> going to ignore this guy!!!!!!". It's like standing in a busy
GE> terminal and yelling around that you're ignoring someone. It's
GE> little more than a poor attempt to get attention. Not unlike what
GE> you do when you see posts you don't like.
you are a flamer since all you say are negative comments about other
posters. show me one perl comment of yours in the last month. or a
positive comment about anything.
and you can plonk me if you wish. i will still defend others who tell
posters how to read the guidelines, the FAQ and such. that is how to
teach better perl.
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: Sat, 10 May 2008 16:57:20 -0700
From: "Gordon Etly" <get@bentsys.com>
Subject: Re: DROP TABLE customers
Message-Id: <68mr31F2tpfgfU1@mid.individual.net>
Uri Guttman wrote:
[please don't lead quoted text with spaces.]
> Gordon Etly <get@bentsys.com> writes:
> > Uri Guttman wrote:
> > > will you ever make a comment about perl code itself?
> > It's not a requirement to comment. It's certainally no concern of
> > yours, as you are not mine nor anyone else's keeper.
> all you ever comment about is how others post things.
It's not the only thing I comment about, but it is perfecly valid in any
group. always has been. If you can't take feedback, don't post.
> this means you are not contributing anything useful.
I could argue the same thing about posts announcing a killfile hit.
> since you don't mention any perl code ever, you have no right
> to post about others.
1) This has NEVER been a requirement to post, and 2) you are assuming
you know my entire posting history, which you most certainly don't. I
spend a good deal of time helping on various lists out there and I have
been using Perl a long time and have followed this and many groups for
over a decade. You stance, attempting to impose an artificial
requirement, is complete rubbish.
> you are a flamer since all you say are negative comments about other
> posters.
Even more backwards rubbish. I merely point out what I don't like. It's
called making a comment about something. It is not automatically a
flame, unless of course it's something the receiving end (and related
parties) obviously don't like to hear, then that person has to be
silenced. Sadly it's a reoccurring thing on UseNet.
--
G.Etly
------------------------------
Date: 10 May 2008 21:08:04 GMT
From: Jo <jo@nosp.invalid>
Subject: FAQ 3.31 == FAQ 3.30
Message-Id: <48260eb4$0$14354$e4fe514c@news.xs4all.nl>
FAQ 3.30 and FAQ 3.31 posted in comp.lang.perl.misc are duplicates.
------------------------------
Date: Sat, 10 May 2008 20:31:57 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Get variable from its name string or vice versa?
Message-Id: <slrng2bqgv.v9m.hjp-usenet2@hrunkner.hjp.at>
On 2008-05-09 18:21, Jens Thoms Toerring <jt@toerring.de> wrote:
> A. Sinan Unur <1usa@llenroc.ude.invalid> wrote:
>> Jerry Krinock <jerry@sheepsystems.com> wrote in news:a2761c7e-8820-4f16-
>> 98d7-64c1bc9ef4e3@k13g2000hse.googlegroups.com:
>> > I have written a function to log variables like this:
>> >
>> > " varName: varValue"
>
>> This is a FAQ:
>
>> perldoc -q "How can I use a variable as a variable name"
>
> I think the OP is looking for something a bit different, i.e.
> a way to get the name of variable from the variable itself.
> I.e. some hypothetical code like
>
> my $x = 10;
> logvar( \$x );
>
> sub logvar {
> my $varref;
> print get_name_from_reference( $var ) . " " . $$var . "\n";
> }
I think what is needed in this case a macro, not a subroutine. You want
to turn
logvar( $x );
into
print '$x' . " " . $x . "\n";
and similarly
logvar( $foo->{bar}{$y} );
into
print '$foo->{bar}{$y}' . " " . $foo->{bar}{$y} . "\n";
Macros are not part of perl per se, but can be implemented via source
filters. It shouldn't be too hard to write a filter like that.
But it happens that Damian Conway already wrote one which might do what
the OP wants: Smart::Comments.
#!/usr/local/bin/perl5.10.0
use warnings;
use strict;
use Smart::Comments;
my $var = 5;
### At <where> ...
### $var
### At <where> ...: $var
__END__
prints:
### At "./foo", line 8 ...
### $var: 5
### At "./foo", line 10 ...: 5
hp
------------------------------
Date: Sat, 10 May 2008 21:14:27 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: I need to extract an array from a scalar regex-wise ?
Message-Id: <x7prrtrhe5.fsf@mail.sysarch.com>
>>>>> "GE" == Gordon Etly <get@bentsys.com> writes:
GE> advice please wireless 802.11 on RH8 wrote:
>> $_ =
>> 'We went to the beach on Monday but it turned out that Sunday would
>> have been better. The weather report Saturday said no rain until
>> Thursday but I asked Tuesday (a trick!) and she said it rained
>> Wednesday.'
>> @days = qw( Monday Sunday Saturday Thursday Tuesday Wednesday )
>>
>> My best shot is:
>> my @days = keys %{ /((mon|tues|wednes|thurs|fri|satur|sun)day)/gi };
>>
>> Which, oddly, doesn't seem to work. I say "oddly", because
>>
>> /((mon|tues|wednes|thurs|fri|satur|sun)day)/gi
>>
GE> I think you want something like this:
GE> Code:
GE> my @days = qw( Sunday Monday Tuesday Wednesday Thursday Friday
GE> aturday );
GE> my @wanted_days = qw( Monday Sunday Saturday Thursday Tuesday
GE> Wednesday );
huh?? he wants to GET those days from the text, not preset them.
GE> my %days = map { $_ => m/(.*)day$/; } @days;
GE> print map { "$_ => $days{$_}\n" } @wanted_days;
and where is the input text being scanned?? that is the issue here, not
how to make a hash of day names.
GE> Is this what you were after?
no it isn't. glad to see you actually make some perl comments. try
better next time.
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: Sat, 10 May 2008 16:49:05 -0700
From: "Gordon Etly" <get@bentsys.com>
Subject: Re: I need to extract an array from a scalar regex-wise ?
Message-Id: <68mqjiF2ssj15U1@mid.individual.net>
Uri Guttman wrote:
> Gordon Etly <get@bentsys.com> writes:
[please don't lead quoted text with spaces]
> > advice please wireless 802.11 on RH8 wrote:
> > > $_ =
> > > 'We went to the beach on Monday but it turned out that Sunday
> > > would have been better. The weather report Saturday said no rain
> > > until Thursday but I asked Tuesday (a trick!) and she said it
> > > rained Wednesday.'
> > >
> > > @days = qw( Monday Sunday Saturday Thursday Tuesday Wednesday )
> > >
> > > My best shot is:
> > > my @days = keys %{
> > > /((mon|tues|wednes|thurs|fri|satur|sun)day)/gi }; >>
> > > Which, oddly, doesn't seem to work. I say "oddly", because
> > >
> > > /((mon|tues|wednes|thurs|fri|satur|sun)day)/gi
> > I think you want something like this:
> >
> > Code:
> > my @days = qw( Sunday Monday Tuesday Wednesday Thursday Friday
> > aturday );
> > my @wanted_days = qw( Monday Sunday Saturday Thursday Tuesday
> > Wednesday );
> huh?? he wants to GET those days from the text, not preset them.
Ok, so I mis-read. After re-reading it seems he just wants to capture
the days of the week from the string, so the answer is simple:
Code:
$_ =
'We went to the beach on Monday but it turned out that Sunday would
have been better. The weather report Saturday said no rain until
Thursday but I asked Tuesday (a trick!) and she said it rained
Wednesday.';
my @days = m#((?:mon|tues|wednes|thurs|fri|satur|sun)day)#gi;
print join(", ", @days);
Output:
Monday, Sunday, Saturday, Thursday, Tuesday, Wednesday
And the code I gave be before can be adapted/modified to change the
format of the day of the week's name.
--
G.Etly
------------------------------
Date: Sun, 11 May 2008 11:25:43 +1200
From: Barb Knox <see@sig.below>
Subject: Re: implementation for Parsing Expression Grammar?
Message-Id: <see-68826E.11254311052008@lust.ihug.co.nz>
In article <48257ab7$0$29576$c83e3ef6@nn1-read.tele2.net>,
Lars Rune Nøstdal <larsnostdal@gmail.com> wrote:
> Hi,
> Finite automata works for "nested things".
Only in the special case when the depth of nesting is bounded ahead of
time. If it's unbounded then there is an unbounded amount of "stack"
information that the automaton needs to remember, therefore a finite
automaton cannot do it.
<pedantry>
That should be "Finite automata WORK ...", since "automata" is plural.
</pedantry>
> http://en.wikipedia.org/wiki/Automata_theory
--
---------------------------
| BBB b \ Barbara at LivingHistory stop co stop uk
| B B aa rrr b |
| BBB a a r bbb | Quidquid latine dictum sit,
| B B a a r b b | altum viditur.
| BBB aa a r bbb |
-----------------------------
------------------------------
Date: Sun, 11 May 2008 02:10:09 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Perl DBI Module: SQL query where there is space in field name
Message-Id: <pan.2008.05.11.00.10.08@rtij.nl.invlalid>
On Sat, 10 May 2008 09:43:15 -0700, szr wrote:
>> Any serious newsreader does not do mime-multipart.
>
> This would seem to be the opposite from what I've seen. All the major
> graphical ones (at least for Windows) to handle it, and they all allow
> you to specify which format should take precedence. I have that set to
> "plain", so I don't actually see the HTML part of a multipart posting
> :-)
I haven't "done" Windows for ages, but I used to use Xnews, which
definately did not do mime-multipart. I'ld be very surprised if anything
besides Outlook and possibly Mozilla and friends do mime-multipart.
M4
------------------------------
Date: Sun, 11 May 2008 02:11:59 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Perl DBI Module: SQL query where there is space in field name
Message-Id: <pan.2008.05.11.00.11.58@rtij.nl.invlalid>
On Sat, 10 May 2008 09:48:46 -0700, Waylen Gumbal wrote:
>> Therefore anything following his signature delimiter line must be his
>> signature.
>
> Only if you look at the raw source of the message, but looking at raw
> source is not what you would do, right? No, you would look at the
> plain-text part of the message, which has a sig 2 lines long.
Uhm, no. Any serios newsreader does not "do" mime-multipart, so normally
reading the message does show a 120+ lines signature.
M4
------------------------------
Date: Sat, 10 May 2008 14:28:49 -0700 (PDT)
From: kronecker@yahoo.co.uk
Subject: Printing a new line
Message-Id: <1581fc33-6137-44a8-b363-d15a016988ab@d19g2000prm.googlegroups.com>
Sounds simple enough.
I am printing to a text file file
open (example, ">remote.txt") || die ("Could not open file. $!");
print example ($first_name);
print example ($last_name);
close (example);
I have tried putting \n but it gives errors. Basically I want the
first and last names on a new line.
thanks
k.
------------------------------
Date: 10 May 2008 21:55:36 GMT
From: jt@toerring.de (Jens Thoms Toerring)
Subject: Re: Printing a new line
Message-Id: <68mjuoF2tsfq0U2@mid.uni-berlin.de>
kronecker@yahoo.co.uk wrote:
> I am printing to a text file file
> open (example, ">remote.txt") || die ("Could not open file. $!");
What about checking that open() did succeed?;-)
> print example ($first_name);
> print example ($last_name);
> close (example);
> I have tried putting \n but it gives errors.
It typically is useful if you tell
a) the exact code you did try ("I have tried putting \n" is rather
vague and could mean a lot of different things)
b) the exact error messages you got.
> Basically I want the first and last names on a new line.
print example "$first_name\n";
print example "$last_name\n";
or, even shorter
print example "$first_name\n$last_name\n";
Regards, Jens
--
\ Jens Thoms Toerring ___ jt@toerring.de
\__________________________ http://toerring.de
------------------------------
Date: Sat, 10 May 2008 22:02:24 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Printing a new line
Message-Id: <1k6c249qkock0cn5mm50kpqs1sdkt9r9pa@4ax.com>
kronecker@yahoo.co.uk wrote:
>open (example, ">remote.txt") || die ("Could not open file. $!");
>print example ($first_name);
> print example ($last_name);
>close (example);
>
>I have tried putting \n
How?
>but it gives errors.
Which?
>Basically I want the
>first and last names on a new line.
Well, yes, adding a "\n" in the output stream will do exactly that under
normal circumstances.
jue
------------------------------
Date: Sat, 10 May 2008 23:01:34 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Printing a new line
Message-Id: <uiihf5-en9.ln1@osiris.mauzo.dyndns.org>
Quoth kronecker@yahoo.co.uk:
> Sounds simple enough.
>
> I am printing to a text file file
>
> open (example, ">remote.txt") || die ("Could not open file. $!");
> print example ($first_name);
> print example ($last_name);
> close (example);
>
> I have tried putting \n but it gives errors. Basically I want the
> first and last names on a new line.
You really need to find and read a basic Perl book. There are two ways
of doing this: print a newline explicitly, like this:
print example ("$first_name\n");
and ask perl to add one to the end of every print statement like this:
$\ = "\n";
print example ($first_name);
print example ($last_name);
Some further points: it's usual in Perl code to make filehandles
all-caps, so they stand out. Also, it's much better to use filehandles
that live in variables than the old global filehandles, and it's much
safer to get into the habit of using the 3-argument form of open, like
this:
open(my $EXAMPLE, '>', 'file.txt')
|| die("can't open file,txt: $!");
Ben
--
Every twenty-four hours about 34k children die from the effects of poverty.
Meanwhile, the latest estimate is that 2800 people died on 9/11, so it's like
that image, that ghastly, grey-billowing, double-barrelled fall, repeated
twelve times every day. Full of children. [Iain Banks] ben@morrow.me.uk
------------------------------
Date: Sat, 10 May 2008 22:09:14 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Printing a new line
Message-Id: <Xns9A9AB8AB4933Fasu1cornelledu@127.0.0.1>
kronecker@yahoo.co.uk wrote in news:1581fc33-6137-44a8-b363-
d15a016988ab@d19g2000prm.googlegroups.com:
> Sounds simple enough.
>
> I am printing to a text file file
>
> open (example, ">remote.txt") || die ("Could not open file. $!");
The recommended convention, if you are going to use bareword
filehandles, is to use all upper case. On the otherhand, such
filehandles are package local which means they can be the source of
hard-to-track bugs. I would recommend:
my $remote_file = 'remote.txt';
open my $example, '>', $remote_file
or die "Cannot open '$remote_file': $!";
> print example ($first_name);
> print example ($last_name);
print $example "$_\n" for ( $first_name, $last_name );
> close (example);
Check on errors on close as well, especially if you opened the file for
writing.
>
> I have tried putting \n but it gives errors.
This is not helpful. Where did you try to put \n?
If you are using 5.10, you can just use the new say function to append a
newline automatically to every line you print.
#!/usr/bin/perl
use strict;
use warnings;
use 5.010;
my ($first_name, $last_name) = qw( first last );
my $remote_file = 'remote.txt';
open my $example, '>', $remote_file
or die "Cannot open '$remote_file': $!";
say $example $_ for ( $first_name, $last_name );
close $example
or die "Error closing '$remote_file': $!";
__END__
C:\Temp> t
C:\Temp> cat remote.txt
first
last
--
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://www.rehabitation.com/clpmisc/
------------------------------
Date: Sat, 10 May 2008 20:56:41 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: regex problem unresolved
Message-Id: <fj1c249dk7j5tfu7v8j377oog6bjth9djr@4ax.com>
"Ela" <ela@yantai.org> wrote:
>the matching string comes from a data file and therefore cannot be known in
>advance.
Good to know.
>It is a cyclic problem that if I had known which line of the perl codes that
>makes regex fail, I might have already solved half of the problem. But I'm
>really saying the truth that no line number printed. And there's a single
>line of error saying "Invalid [] range "l-c" in regex; marked by <-- HERE in
>m/^3-oxoacyl-[acyl-c
><-- HERE arrier protein] reductase fabg1$/"
Then your data file contains an illegal regular expression:
^3-oxoacyl-[acyl-carrier protein] reductase fabg1$
is not a valid RE. Sorry, but that's what it is. Broken data!
Some options:
- fix that broken data file. If that data file is supposed to contain
REs, then you have to make sure that it does contain REs and not illegal
expressions
- invent some method to convert the broken RE into a valid RE before
applying it in the pattern match. I cannot tell you how because I do not
know what the intended behaviour would be.
BUT: You do know what a character class is, do you? Does your data file
really really meant to match exactly one character of the set a, c, e,
l, n, p, o, i, r, t, y, and space at that spot? Because that is what is
defined in that character class (ignoring the error for the time being)!
I have a very strong feeling that you did _NOT_ mean to use a regular
expression match in the first place but that you simply meant to compare
the text with some other text. After all, the orginal author went even
so far as to anchor the RE at the beginning and end of the RE and the RE
doesn't use any meaningful RE metacharacters at all.
Therefore I suggest to investigate option 3:
- don't use any RE match but a simple string comparison instead unless
you need the added functionality of an RE match
>Xho suggested 2 solutions. One is index instead of regex that I still don't
>know what it means.
See perldoc -f index
index() is _the_ standard way to check if one string is a substring of
another string.
However in your case because the RE is anchored at both ends a simple
'eq' would work even better.
>Another one is to upgrade perl, which is impossible.
You still might consider doing it at least temporarily just to chase
down this bug.
>I appreciate your comments/critics what can be done to maximize the chance
>to solve this problem.
Think very, very hard if you really, really meant RE pattern matching or
if you meant to do literal string comparison. These are two very
different things and I have a very strong feeling that you are trying to
use hammer to drive a screw.
jue
------------------------------
Date: Sun, 11 May 2008 01:02:50 +0000 (UTC)
From: Ben Bullock <benkasminbullock@gmail.com>
Subject: Re: regex problem unresolved
Message-Id: <g05gjp$111$1@ml.accsnet.ne.jp>
On Sun, 11 May 2008 00:24:25 +0800, Ela wrote:
> I was suggested by experts to post runnable codes to seek advice.
> Unfortunately, after 4-day trial, I'm unable to break down the large
> codes written by others to a smaller one. And as what xhoster inferred
> exactly, the matching string comes from a data file and therefore cannot
> be known in advance.
So, to make this clear, somewhere in your code there is something of the
form of
$matchingstring = <DATAFILE>;
if (/$matchingstring/) { #
print "Hallo Ela!\n"
}
> It is a cyclic problem that if I had known which line of the perl codes
> that makes regex fail, I might have already solved half of the problem.
> But I'm really saying the truth that no line number printed.
Jurgen Exner dug up that this isn't printed with Perl 5.6. It's a shame
if you can't upgrade. Could you please confirm that you are using Perl
5.6 by printing the results of
perl --version
> And there's
> a single line of error saying "Invalid [] range "l-c" in regex; marked
> by <-- HERE in m/^3-oxoacyl-[acyl-c
> <-- HERE arrier protein] reductase fabg1$/"
What you need to do is to use \Q \E around the string which is causing
the problems. In my example code:
if (/\Q$matchingstring\E/) { #
print "Hallo Ela!\n"
}
But that doesn't help you to find the line with the problem.
> Xho suggested 2 solutions. One is index instead of regex that I still
> don't know what it means.
He means you should use the function "index" instead of / / in the above
code.
> Another one is to upgrade perl, which is
> impossible.
As far as I know, it's possible to install Perl into a local account. It
doesn't have to be installed globally. The last time I did this was about
1996, so I'm not 100% sure about nowadays, but I'm fairly sure it should
be possible.
> In fact, since input data file is needed and "oxoacyl" does exist in
> that data file confirmed by search, I believe the fetch program first
> grabs all the keywords and later uses the variable one by one to match.
So the problem is where the match is taking place? To find the line where
the match is taking place involves carefully looking at the source code.
Unfortunately there is no particular magic trick which will solve this
problem for you. You will have to actually understand what the program is
doing to solve this problem. In these circumstances one useful start is
to sprinkle "print" statements throughout the code.
------------------------------
Date: Sat, 10 May 2008 17:39:42 -0400
From: Lew <lew@lewscanon.com>
Subject: Re: The Importance of Terminology's Quality
Message-Id: <UNadnSyhW72Ci7vVnZ2dnUVZ_uSdnZ2d@comcast.com>
Sherman Pendley wrote:
> Lew <lew@lewscanon.com> writes:
>
>> You guys are off topic. None of the million groups to which this
>> message was posted are about netiquette.
>
> Netiquette has come up at one point or another in pretty much every
> group I've ever read. It's pretty much a universal meta-topic.
Good, then please have the courtesy not to include comp.lang.java.programmer
in the distribution for this thread any longer.
--
Lew
------------------------------
Date: Sat, 10 May 2008 21:01:21 -0400
From: George Neuner <gneuner2/@/comcast.net>
Subject: Re: The Importance of Terminology's Quality
Message-Id: <3jgc2498f1te1uqh7rrf3odhevkrt3s75e@4ax.com>
On Fri, 09 May 2008 22:45:26 -0500, rpw3@rpw3.org (Rob Warnock) wrote:
>George Neuner <gneuner2/@/comcast.net> wrote:
>
>>On Wed, 7 May 2008 16:13:36 -0700 (PDT), "xahlee@gmail.com"
>><xahlee@gmail.com> wrote:
>
>>>• Functions [in Mathematica] that takes elements out of list
>>>are variously named First, Rest, Last, Extract, Part, Take,
>>>Select, Cases, DeleteCases... as opposed to “car”, “cdr”,
>>>“filter”, “filter”, “pop”, “shift”, “unshift”, in lisps and
>>>perl and other langs.
>
>>| Common Lisp doesn't have "filter".
>
>Of course it does! It just spells it REMOVE-IF-NOT!! ;-} ;-}
I know. You snipped the text I replied to.
Xah carelessly conflated functions snatched from various languages in
an attempt to make some point about intuitive naming. If he objects
to naming a function "filter", you can just imagine what he'd have to
say about remove-if[-not].
George
--
for email reply remove "/" from address
------------------------------
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 1530
***************************************
