[23708] in Perl-Users-Digest
Perl-Users Digest, Issue: 5914 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Dec 9 06:05:38 2003
Date: Tue, 9 Dec 2003 03:05:07 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 9 Dec 2003 Volume: 10 Number: 5914
Today's topics:
#!/usr/bin/perl <roman@sky.lviv.ua>
Re: #!/usr/bin/perl <noreply@gunnar.cc>
Re: #!/usr/bin/perl <kuujinbo@hotmail.com>
Re: #!/usr/bin/perl <karlheinz.weindl@oooonlinehome.de>
Re: #!/usr/bin/perl <roman@sky.lviv.ua>
Re: Am I right on Mod_Perl? <matthew.garrish@sympatico.ca>
Re: Another sort question. (Anno Siegel)
escape sequence for tab not working (dn_perl@hotmail.com)
Re: escape sequence for tab not working (Anno Siegel)
Re: Getting return code from a child process <Peter.Dintelmann@dresdner-bank.no-spam.de>
Re: How to open a file from the end and read the last 1 <nmihai_year_2000@yahoo.com>
Re: open/seek vs IO::Open/setpos news@roaima.freeserve.co.uk
Perl Benchmark: no chance for Pentium 4 and AMD Athlon <founder@pege.org>
Re: Perl script to process file list.... <matthew.garrish@sympatico.ca>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Scp files to another server help <jwillmore@remove.adelphia.net>
Re: Scp files to another server help <jim.mozley@exponential-e.com>
Re: What is the Best Content Management System? <karim3411@!!yahoo!!.com>
Re: What is the Best Content Management System? (Jochen Buennagel)
Re: Why can't I parse google search results? (bob)
Re: Why can't I parse google search results? <asu1@c-o-r-n-e-l-l.edu>
Re: Why can't I parse google search results? <bigiain@mightymedia.com.au>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 9 Dec 2003 10:37:02 +0200
From: "Roman Khutkyy" <roman@sky.lviv.ua>
Subject: #!/usr/bin/perl
Message-Id: <br41p3$2gj5$1@news.uar.net>
Hi all,
is there any ability in Perl to write the first string in script as
alternative string for different platforms.
I write CGI scripts on the Win32 computer, then I transport it to the Unix
server, and each time i need to rewrite this string. Is there universal
string for both platforms?
------------------------------
Date: Tue, 09 Dec 2003 09:41:04 +0100
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: #!/usr/bin/perl
Message-Id: <br42ds$25robq$1@ID-184292.news.uni-berlin.de>
Roman Khutkyy wrote:
> is there any ability in Perl to write the first string in script as
> alternative string for different platforms.
> I write CGI scripts on the Win32 computer, then I transport it to
> the Unix server, and each time i need to rewrite this string. Is
> there universal string for both platforms?
On my Win32 computer, I have a C:/usr/bin directory where I have an
extra copy of perl.exe. That makes '#!/usr/bin/perl' work there as well.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Tue, 09 Dec 2003 18:31:58 +0900
From: ko <kuujinbo@hotmail.com>
Subject: Re: #!/usr/bin/perl
Message-Id: <br451l$2po$1@pin3.tky.plala.or.jp>
Roman Khutkyy wrote:
> Hi all,
> is there any ability in Perl to write the first string in script as
> alternative string for different platforms.
> I write CGI scripts on the Win32 computer, then I transport it to the Unix
> server, and each time i need to rewrite this string. Is there universal
> string for both platforms?
>
>
If you're using Active State Perl you can keep the shebang line intact -
its ignored, *except* for any switches.
'perldoc perlrun' ('Description' section) describes this behavior.
HTH - keith
------------------------------
Date: Tue, 09 Dec 2003 11:19:42 +0100
From: Karlheinz Weindl <karlheinz.weindl@oooonlinehome.de>
Subject: Re: #!/usr/bin/perl
Message-Id: <br47ko$4ok$1@online.de>
ko schrieb:
> Roman Khutkyy wrote:
>
>> Hi all,
>> is there any ability in Perl to write the first string in script as
>> alternative string for different platforms.
>> I write CGI scripts on the Win32 computer, then I transport it to the
>> Unix
>> server, and each time i need to rewrite this string. Is there universal
>> string for both platforms?
>>
>>
>
> If you're using Active State Perl you can keep the shebang line intact -
> its ignored, [...]
Not necessarily true. The OP transfers CGI scripts from Win32 to UNIX,
so presumably running Apache under Windows, which in turn requires the
shebang line to be present (and correct of course).
------------------------------
Date: Tue, 9 Dec 2003 13:04:26 +0200
From: "Roman Khutkyy" <roman@sky.lviv.ua>
Subject: Re: #!/usr/bin/perl
Message-Id: <br49sj$2l5n$1@news.uar.net>
Yes it works when you are using ISS, but under Apache it needs correct path.
"Gunnar Hjalmarsson" <noreply@gunnar.cc> wrote in message
news:br42ds$25robq$1@ID-184292.news.uni-berlin.de...
> Roman Khutkyy wrote:
> > is there any ability in Perl to write the first string in script as
> > alternative string for different platforms.
> > I write CGI scripts on the Win32 computer, then I transport it to
> > the Unix server, and each time i need to rewrite this string. Is
> > there universal string for both platforms?
>
> On my Win32 computer, I have a C:/usr/bin directory where I have an
> extra copy of perl.exe. That makes '#!/usr/bin/perl' work there as well.
>
> --
> Gunnar Hjalmarsson
> Email: http://www.gunnar.cc/cgi-bin/contact.pl
>
------------------------------
Date: Mon, 8 Dec 2003 19:46:27 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Am I right on Mod_Perl?
Message-Id: <yX8Bb.10838$3y1.941025@news20.bellglobal.com>
"Tad McClellan" <tadmc@augustmail.com> wrote in message
news:slrnbt9mka.q4f.tadmc@magna.augustmail.com...
> David K. Wall <usenet@dwall.fastmail.fm> wrote:
> >
> > "the best way to get accurate information on Usenet is to post
> > something wrong and wait for corrections"
>
>
> Pigs can fly!
>
It would stand to reason, as I remember well watching Pigs in Space...
Matt
------------------------------
Date: 9 Dec 2003 09:49:12 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Another sort question.
Message-Id: <br45qo$h4e$1@mamenchi.zrz.TU-Berlin.DE>
A. Sinan Unur <asu1@c-o-r-n-e-l-l.edu> wrote in comp.lang.perl.misc:
> mpatt644@yahoo.com (Mal) wrote in news:66f79aeb.0312081510.8a12e64
> @posting.google.com:
>
> > I figured out that replacing
> >
> > $aHourField <=> $bHourField with
> > (($aHourField+17) %24) <=> (($bHourField+17) %24)
> >
> > does what I need.
>
> Could you explain that please?
With a 24-hour clock it shifts the start of day from midnight to 7 am.
Anno
------------------------------
Date: 8 Dec 2003 23:32:54 -0800
From: dn_perl@hotmail.com (dn_perl@hotmail.com)
Subject: escape sequence for tab not working
Message-Id: <97314b5b.0312082332.696aadde@posting.google.com>
I am unable to print a tab using "\t" sequence in a file
which has some database related statements.
I am using perl on a solaris server with Oracle.
In some_dbi.pl, the patch is : \t prints as single character.
--------
my $this_str, $sub_str ;
$sub_str = "abc" ;
$this_str = sprintf "%s\t%s", $sub_str, $sub_str ;
system( "echo $this_str") ;
--------
In ch.pl, the patch is : \t prints as tab-character.
--------
$sub_str = "abc" ;
$this_str = sprintf "%s\t%s", $sub_str, $sub_str ;
print $this_str ;
--------
What could be causing this behaviour? I want \t to print
as tab .
TIA.
------------------------------
Date: 9 Dec 2003 10:30:25 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: escape sequence for tab not working
Message-Id: <br4881$jvg$1@mamenchi.zrz.TU-Berlin.DE>
dn_perl@hotmail.com <dn_perl@hotmail.com> wrote in comp.lang.perl.misc:
> I am unable to print a tab using "\t" sequence in a file
> which has some database related statements.
>
> I am using perl on a solaris server with Oracle.
>
> In some_dbi.pl, the patch is : \t prints as single character.
I don't think "patch" is the word you want to use here.
The behavior of your code is correct and must be expected.
> --------
> my $this_str, $sub_str ;
There are parentheses missing around the variables. Are you running
under strict and warnings? You should.
> $sub_str = "abc" ;
> $this_str = sprintf "%s\t%s", $sub_str, $sub_str ;
This sets $this_str to "abc", followed by a literal tab, followed by
"abc".
> system( "echo $this_str") ;
> --------
When you use system() in this form, it calls a shell to execute the
command given. The string the shell sees is "echo abc abc", where
the white space between the two "abc" is a tab. The shell, however,
doesn't care in what form or amount whitespace is given between words,
it just splits the command into words. So echo doesn't get to see
a tab at all, all it knows it has to echo the word "abc" twice, and
that's what it does.
> In ch.pl, the patch is : \t prints as tab-character.
> --------
> $sub_str = "abc" ;
> $this_str = sprintf "%s\t%s", $sub_str, $sub_str ;
> print $this_str ;
> --------
Here Perl prints the value without shell intervention. The tab character
is displayed as such.
> What could be causing this behaviour? I want \t to print
> as tab .
Why do you want to print the string via system() and "echo"? Perl
can print strings just fine. I don't think you'll need the following
information.
Your question is more about the shell than about Perl. You need to find
out how to make your shell's "echo" (or the system's /bin/echo) print a
tab character. For my sh, that's 'echo -e "abc\tabc"' (note inner quotes).
That string, in Perl, is written $str = '"abc\\tabc"'. The "\" must
be doubled because it is a quoting character even in single quotes.
So your sprintf should look like
$this_str = sprintf '"%s\\t%s"', $sub_str, $sub_str;
Then
system "echo $this_str";
will print the tab.
Anno
------------------------------
Date: Tue, 9 Dec 2003 10:55:18 +0100
From: "Peter Dintelmann" <Peter.Dintelmann@dresdner-bank.no-spam.de>
Subject: Re: Getting return code from a child process
Message-Id: <br44oe$c0r7@news-1.bank.dresdner.net>
Hi Jon,
"Jon" <jhayden@usa.com> wrote in message
news:28769dad.0312080419.1fcbce29@posting.google.com...
> Ben & Jim,
>
> Thanks guys. You gave me some great information. I can do what I need to
do now.
and please have an additional look at the macros
WIFEXITED and WEXITSTATUS from the POSIX
module (they make code much more readable then
"$? >> 8").
Peter
------------------------------
Date: Tue, 09 Dec 2003 07:54:54 GMT
From: "Mihai N." <nmihai_year_2000@yahoo.com>
Subject: Re: How to open a file from the end and read the last 100 lines
Message-Id: <Xns944BF3580C0C1MihaiN@216.148.227.77>
I am afraid this is going way too far.
Did you ever wasted several hours with a module that was buggy,
or just not good enough for what you needed?
But this is not about this.
I was just trying to tell that there is something in between
"always rool your own" and "always use CPAN".
What bothers me is the "always" part.
I think there is no such thing as black or white, there is always
about gray levels, and any extreme is bad.
I would not try to write my own sendmail, db, or ftp routines
(in fact I do have quite a few scripts using modules developed by
others).
Where is the balance? I don't know. I guess it is not the same
for all (it would be borring). Even for me the line is moving.
If I am in a hurry, if I want to learn something new, if I'm tired.
Right now I'm tired of this discution. Sorry.
--
Mihai
-------------------------
Replace _year_ with _ to get the real email
------------------------------
Date: Tue, 9 Dec 2003 09:11:50 +0000
From: news@roaima.freeserve.co.uk
Subject: Re: open/seek vs IO::Open/setpos
Message-Id: <m7gga1-e9a.ln1@news.roaima.co.uk>
Joost Diepenmaat <joost@rot13-ubeghf-zrpunavphf-rot13.net> wrote:
>> $h->setpos (0) or warn "setpos: $!\n";
> setpos does not do wat you think it does; from the IO::Seekable
> manpage:
> $io->setpos
> Uses the value of a previous getpos call to return to
> a previously visited position. Returns "0 but true" on
> success, "undef" on failure.
Hmm. Yes had I read this - but assumed that getpos() would return a (perl)
integer offset into the file like its C library counterpart. Unfortunately
it transpires that it doesn't - it's an opaque (string/binary) value.
Thanks for (re-)pointing this out!
Now, do you have any suggestions for the next paragraph in that same page:
$io->setpos ( POS, WHENCE )
Seek the IO::File to position POS, relative to WHENCE:
WHENCE=0 (SEEK_SET)
POS is absolute position. (Seek relative to the start
of the file)
I can't get this to work at all - I get a runtime usage error,
"Usage: IO::Seekable::setpos(handle, pos) at ..."
e.g.
$h = new IO::File ... # O_RDWR or "+> file", etc.
$h->print ...
$h->setpos (0, SEEK_SET) # use Fcntl qw/:DEFAULT :seek/
Thoughts?
Chris
--
@s=split(//,"Je,\nhn ersloak rcet thuarP");$k=$l=@s;for(;$k;$k--){$i=($i+1)%$l
until$s[$i];$c=$s[$i];print$c;undef$s[$i];$i=($i+(ord$c))%$l}
------------------------------
Date: Tue, 9 Dec 2003 09:51:48 +0100
From: =?Windows-1252?Q?Roland_M=F6sl?= <founder@pege.org>
Subject: Perl Benchmark: no chance for Pentium 4 and AMD Athlon
Message-Id: <3fd58d43$0$54464$91cee783@newsreader02.highway.telekom.at>
I developt since 1997 a web design software completly
written in Perl.
On the Windows part, I user Perl built 522 from Active State
Now I made some Benchmarks with a big site.
The software creates around 600 web pages out of a database
during the benchmark.
The results had been very surprising:
Notebook Acer Travelmate 663 LMI 512 MB RAM
1.6 GHz Pentium-M...............................4:35
Notebook Acer Travelmate 802 LMI 512 MB RAM
1.5 GHz Pentium-M...............................4:54
Notebook Acer Travelmate 663 LMI 512 MB RAM
1.3 GHz Pentium-M...............................5:25
Desktop 512 MB RAM
Ahtlon +2500........................................7:06
Notebook Acer Travelmate 634 LCI 512 MB RAM
1.8 GHz mobile Pentium 4M..................7:14
Desktop 512 MB RAM
Athlon +2000........................................7:30
Notebook Gericom Hummer Advanced 512 MB RAM
Athlon +2500........................................8:11
Notebook 512 MB RAM
Athlon +1500.......................................12:40
Notebook Gericom Silver Seraph 256 MB RAM
mobile Celeron 500..............................33:11
Surprise 1: 1.6 GHz Centrino nearly 7 times faster than
500 MHz Celeron
Surprise 2: Ahtlon extrem slow
Surprise 3: The test seems to indicate, that a 1.7 GHz Centrino
is faster than (not tested until now) a 3.06 GHz P4
Has somebody an explanation why this Perl based benchmark
shows so big advantage for the new Pentium-M
--
Roland Mösl
http://www.pege.org Clear targets for a confused civilization
http://web-design-suite.com Web Design starts at the search engine
------------------------------
Date: Mon, 8 Dec 2003 21:05:52 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Perl script to process file list....
Message-Id: <u6aBb.11461$3y1.974501@news20.bellglobal.com>
"Jim Carter" <carterave@yahoo.com> wrote in message
news:9c2a26b6.0312081736.593a8686@posting.google.com...
> Hi all,
>
> Below is the issue I am working on in Windows 2000.
>
> I have directory, C:\Carter and it it has around 100 file names (ex:
> test1.txt, test2.txt, test3.txt......test100.txt).
>
> 1. First, I need another list with all these 100 file names with no
> ".txt" extension at the end (ex: test1, test2,test3, ....test100).
> 2. Then I want these two lists as key and value pair in a hash.
> (EX: test1, test1.txt, test2, test2.txt, test3, test3.txt, ......,
> test100, test100.txt).
>
> I am struggling with the code to get the final hash. Can some one help
> me out?
>
It makes it difficult to help when you don't post your code.
Matt
------------------------------
Date: Tue, 09 Dec 2003 02:23:40 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <ZoydnX0HQ5YRG0iiRVn-vw@august.net>
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.4 $)
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.
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://mail.augustmail.com/~tadmc/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
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_group_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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 09 Dec 2003 05:53:15 GMT
From: James Willmore <jwillmore@remove.adelphia.net>
Subject: Re: Scp files to another server help
Message-Id: <20031209005314.1ab6c964.jwillmore@remove.adelphia.net>
On 8 Dec 2003 18:05:19 -0800
joel@tradersunited.com (JennAshton) wrote:
> I wrote a simple scp script from my server to pacman server which
> copies all jpg files to /jennash/ directory.
>
> Now, I need help with this script. I would like it to pull not just
> *.jpg files but other file types as well. Also, is it possible to
> pull only files that is 3 minutes old? Please help.
>
> Thanks!
>
> JennAsh
>
> #!/usr/bin/perl
>
> system('scp /export/www/docs/*.jpg pacman:/export/www/jennash/');
>
> exit;
You could check out the Net::SCP and File::Find modules. What you
have written could have been done in *any* *NIX shell - for as little
Perl you have in it.
--
Jim
Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.
a fortune quote ...
You should never wear your best trousers when you go out to fight
for freedom and liberty. -- Henrik Ibsen
------------------------------
Date: Tue, 09 Dec 2003 10:16:25 +0000
From: Jim Mozley <jim.mozley@exponential-e.com>
Subject: Re: Scp files to another server help
Message-Id: <br47ci$295akd$1@ID-201189.news.uni-berlin.de>
JennAshton wrote:
> I wrote a simple scp script from my server to pacman server which
> copies all jpg files to /jennash/ directory.
This answer is not perl related directly, but I moved from using scp to
rsync for this type of thing. The perl bit is that once files were
transferred I then needed to do other tasks (e.g. sighup a daemon) so I
used the perl script which did the rsync to perform other tasks.
Jim
------------------------------
Date: Mon, 8 Dec 2003 21:34:58 -0800
From: Karim <karim3411@!!yahoo!!.com>
Subject: Re: What is the Best Content Management System?
Message-Id: <1lum8e1kaz05j.1kdur5dum2d4t.dlg@40tude.net>
On Mon, 08 Dec 2003 23:27:26 GMT, Liberal wrote:
> There are a few in Perl and PHP, with MySQL or without and either in
> Mod_Perl or not in.
>
> I have heard mason, but it does not have any demo site, but claims, AMAZON
> is using it.
>
> I also like PostNuke, but then there is a sister product caled PHPNuke
>
> I am looking for something simple but with a lot of plug-ins. I will not use
> many features, but like to have BBS/Forum and Classified Ads. I want it
> simple, because I need to rewrite a lot of codes to include my current Perl
> program.
>
> What is my best choice?
Check out http://www.cmsinfo.org
--
Karim
http://www.cheapesthosting.com/webmastertoolbox - Free resources for
Webmasters
------------------------------
Date: 9 Dec 2003 02:14:03 -0800
From: zang@buennagel.com (Jochen Buennagel)
Subject: Re: What is the Best Content Management System?
Message-Id: <5e29e7f2.0312090214.7468a844@posting.google.com>
"Liberal" <test@test.com> wrote:
> What is my best choice?
go to http://opensourcecms.com/
They have over 40 PHP systems installed that you can have a look at,
including full admin access.
From the info in your post you should definitely have a look at Mambo
------------------------------
Date: 8 Dec 2003 21:10:21 -0800
From: utsuxs@hotmail.com (bob)
Subject: Re: Why can't I parse google search results?
Message-Id: <51c3a5d3.0312082110.2b8e8c48@posting.google.com>
My code is short. I didn't post my code because I was neglectful and
I thought I supplied enough information for the gist of my question.
use LWP::Simple;
use HTML::Parse;
use HTML::FormatText;
$html = get("http://www.google.com/search?q=smeghead");
defined $html or die "Can't fetch HTML from http://www.perl.com/";
$ascii = HTML::FormatText->new->format(parse_html($html));
print $ascii;
AS I mentioned earlier this works for yahoo but not google. Since it
works with yahoo I don't believe there is a problem with the code, but
with google. Or is there a problem with the code?
I thank those of you who suggested the google apis. If google is
blocking my requests with the default LWP User-Agent header, then
obviously I have to make some changes.
Thank you.
------------------------------
Date: 9 Dec 2003 05:48:40 GMT
From: "A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu>
Subject: Re: Why can't I parse google search results?
Message-Id: <Xns944C841ECC43asu1cornelledu@132.236.56.8>
utsuxs@hotmail.com (bob) wrote in news:51c3a5d3.0312082110.2b8e8c48
@posting.google.com:
> My code is short. I didn't post my code because I was neglectful and
> I thought I supplied enough information for the gist of my question.
And others have already answered your question.
> use LWP::Simple;
> use HTML::Parse;
> use HTML::FormatText;
> $html = get("http://www.google.com/search?q=smeghead");
> defined $html or die "Can't fetch HTML from http://www.perl.com/";
> $ascii = HTML::FormatText->new->format(parse_html($html));
> print $ascii;
>
> AS I mentioned earlier this works for yahoo but not google. Since it
> works with yahoo I don't believe there is a problem with the code, but
> with google. Or is there a problem with the code?
Try
lwp-request http://www.google.com/search?q=smeghead > t.html
on the command line and view the file in your browser.
--
A. Sinan Unur
asu1@c-o-r-n-e-l-l.edu
Remove dashes for address
Spam bait: mailto:uce@ftc.gov
------------------------------
Date: Tue, 09 Dec 2003 18:41:05 +1100
From: Iain Chalmers <bigiain@mightymedia.com.au>
Subject: Re: Why can't I parse google search results?
Message-Id: <bigiain-BA21C1.18410509122003@news.fu-berlin.de>
In article <51c3a5d3.0312082110.2b8e8c48@posting.google.com>,
utsuxs@hotmail.com (bob) wrote:
> My code is short. I didn't post my code because I was neglectful and
> I thought I supplied enough information for the gist of my question.
>
>
> use LWP::Simple;
> use HTML::Parse;
> use HTML::FormatText;
> $html = get("http://www.google.com/search?q=smeghead");
> defined $html or die "Can't fetch HTML from http://www.perl.com/";
> $ascii = HTML::FormatText->new->format(parse_html($html));
> print $ascii;
>
> AS I mentioned earlier this works for yahoo but not google. Since it
> works with yahoo I don't believe there is a problem with the code, but
> with google. Or is there a problem with the code?
>
> I thank those of you who suggested the google apis. If google is
> blocking my requests with the default LWP User-Agent header, then
> obviously I have to make some changes.
You can't parse it because you're not getting it. You don't have a
parsing problem - try printing $html - google isn't sending you anything.
And yes, it _is_ because of your UserAgent, and as others have pointed
out, using the google api is the way google would like you to solve your
problem.
big
--
'When I first met Katho, she had a meat cleaver in one hand and
half a sheep in the other. "Come in", she says, "Hammo's not here.
I hope you like meat.' Sharkey in aus.moto
------------------------------
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.
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 5914
***************************************
