[26851] in Perl-Users-Digest
Perl-Users Digest, Issue: 8870 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jan 20 06:05:33 2006
Date: Fri, 20 Jan 2006 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 Fri, 20 Jan 2006 Volume: 10 Number: 8870
Today's topics:
Matching subsets of two strings <jweeb2342@hotmail.com>
Re: Matching subsets of two strings (Anno Siegel)
Maybe difficult for English Users - but I ask anyway <kigar@gmx.net>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: randomly choose some uniq elements of an array <noreply@gunnar.cc>
soap::lite for activeperl 5.8 <nospam@home.com>
Re: soap::lite for activeperl 5.8 <sisyphus1@nomail.afraid.org>
Trouble using LIB.PM to modify @INC <nospam@thanksanyway.org>
Re: Trouble using LIB.PM to modify @INC <nospam@thanksanyway.org>
Using RegExp to locate a part of scalar <NoSPam@NoSpam.com>
Re: Validating massive amounts of external links <njus@larshaugseth.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 20 Jan 2006 01:25:05 -0000
From: Jim Weeb <jweeb2342@hotmail.com>
Subject: Matching subsets of two strings
Message-Id: <GS1ASAT338737.3924189815@reece.net.au>
Can anyone offer some help with perl and a script operating a
mail2news gateway?
I'm using CPAN module email:simple so, I can get the groups into
variables using:
$newsgroups=$mail->header("Newsgroups");
$followupto=$mail->header("Followup-To");
Now, when processing the message, I only want to allow
followupto groups that are present in newsgroups - not any
alternative group(s). Group(s) in followupto may be listed in a
different order to those in the original newsgroups line.
I guess I need to combine the groups in each variable into an
array:
@newsgroups2 = split /,/ , $newsgroups ;
@followupto2 = split /,/ , $followupto ;
and then somehow see which items are in both arrays and write
those that are to a new variable $followupto3 (or even back to
the original $followupto)
I guess it would be done with two nested loops, however someone
previously mentioned something about a hash with regard to a
similar problem (and lost me completely). It could probably all
be done in one or two lines by a perl boffin, but unfortunately
my perl, although improving slowly, isn't quite up to the task.
Thanks.
------------------------------
Date: 20 Jan 2006 10:01:30 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Matching subsets of two strings
Message-Id: <dqqcdq$i40$1@mamenchi.zrz.TU-Berlin.DE>
Jim Weeb <jweeb2342@hotmail.com> wrote in comp.lang.perl.misc:
> Can anyone offer some help with perl and a script operating a
> mail2news gateway?
>
> I'm using CPAN module email:simple so, I can get the groups into
> variables using:
>
> $newsgroups=$mail->header("Newsgroups");
> $followupto=$mail->header("Followup-To");
>
> Now, when processing the message, I only want to allow
> followupto groups that are present in newsgroups - not any
> alternative group(s). Group(s) in followupto may be listed in a
> different order to those in the original newsgroups line.
>
> I guess I need to combine the groups in each variable into an
> array:
>
> @newsgroups2 = split /,/ , $newsgroups ;
> @followupto2 = split /,/ , $followupto ;
>
> and then somehow see which items are in both arrays and write
> those that are to a new variable $followupto3 (or even back to
> the original $followupto)
>
> I guess it would be done with two nested loops, however someone
> previously mentioned something about a hash with regard to a
> similar problem (and lost me completely). It could probably all
> be done in one or two lines by a perl boffin, but unfortunately
> my perl, although improving slowly, isn't quite up to the task.
See the faq "How do I compute the difference of two arrays? ..."
(perldoc -q difference).
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
------------------------------
Date: Fri, 20 Jan 2006 09:18:38 +0100
From: "Reinhard Glauber" <kigar@gmx.net>
Subject: Maybe difficult for English Users - but I ask anyway
Message-Id: <43d09cdc$0$20775$9b4e6d93@newsread4.arcor-online.net>
DQoNCkkgZmV0Y2ggIGFuIEhUTUwgU2l0ZSwgdGhyb3VnaCBvdXQgYWxsIHRoZSA8PiBUQUdTLCBz
byB0aGF0IEkgZ2V0IHBsYWluIHRleHQsIHNlYXJjaCBmb3Igc29tZSB3b3JkcyBhbmQNCnNhdmUg
dGhlbSB0byBhIE1ZU1FMIERhdGFiYXNlDQoNClRoYXQgYWxsIHNlZW1zIHRvIHdvcmsgZXhjZXB0
IHRoZSBjb3JyZWN0IGRpc3BsYXkgb2YgIuQiICL2IiAi/CIgDQoNClf2cmwgaXMgc2F2ZWQgYXMg
V8O2cmwNCg0KSSB0cmllZCB1dGYtOCBkZWNvZGluZyAvZW5jb2RpbmcNCg0KdXRmLTggZGVjb2Rp
bmcgd2lsbCBzaG93IHRoZSB3b3JkIGNvcnJlY3QgaW4gdGhlIExpbnV4IHNoZWxsIGJ1dCBub3Qg
aW4gdGhlIGRhdGFiYXNlIDooDQpJIGhhdmUgYSBLYW5vdGl4IChEZWJhaW4pIENvbXB1dGVyIHdo
ZXJlIEkgdHJ5IHRoZSBTY3JpcHQuIFBlcmwgaXMgdXAgdG8gZGF0ZSwgTVlTUUwgaXMgNS4wLjE4
DQoNCkxpbnV4LVNoZWxsOiBJTlNFUlQgSU5UTyBUYWJlbGxlIChOQU1FLCBTVFJBU1NFLi4uLi4p
IFZBTFVFUyAoJ1f2cmwgR21iSCcsJ0thcmxzYmVyZyAuLi4uLi4uLi4pDQoNClRoZSBjaGFyc2V0
IG9mIHRoZSBkYXRhYmFzZSBpcyBjb25maWd1cmVkIGFzIHV0Zi04LCBjb2xsYXRpb24gYXMgdXRm
OF9nZW5lcmFsX2NpDQoNCkkgYWxzbyB0cmllZCB3aXRoIHRoZSBNb2R1bCBIVE1MOjpGb3JtYXRU
ZXh0IHdoaWNoIGNvbnZlcnRzIGh0bWwgdG8gYXNjaWksIGJ1dCBzYW1lIHByb2JsZW0gLi4uDQoN
CkkgcmVhbGxheSBuZWVkIHRoaXMgc2NyaXB0IHRvIHdvcmssIHNvIG1heWJlIG9uZSBoYXMgYW4g
Z29vZCBpZGVhLg0KDQpUaGFua3MsIHRoYW5rcywgdGhhbmtzDQo=
------------------------------
Date: 20 Jan 2006 08:22:16 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <43d09db8$0$1764$8b463f8a@news.nationwide.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.5 $)
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://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
"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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Fri, 20 Jan 2006 01:10:19 +0100
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: randomly choose some uniq elements of an array
Message-Id: <43anvcF1ma1mgU1@individual.net>
xhoster@gmail.com wrote:
> Gunnar Hjalmarsson wrote:
>>please check out this thread, where this
>>issue was discussed in considerable detail:
>>http://groups.google.com/group/comp.lang.perl.misc/browse_frm/thread/da70
>>5489201879ba
>
> Er, what I got out of that thread was that when the list is small, the FAQ
> way is better
This is how I read that thread: One of the FAQ ways is clearly slower
for small arrays, and the other FAQ way may or may not be slower
depending on whether you take into account the time for loading the
module and which platform you are on.
>>The FAQ discusses shuffling of a whole array, while the
>>OP wanted to pick a few elements.
>
> As I said, the optimizations that this allows are almost certainly not
> worthwhile.
I fail to see why the shuffle entry in the FAQ would be an appropriate
starting point in the first place for the problem described by the OP. I
also fail to see how you can be so certain that the OP's list of files
would be large enough to make the FAQ's shuffle approaches relevant from
an efficiency point of view.
>>Xho, did you read the rest of the thread before posting your follow-up?
>
> There is no such thing as "the rest of the thread".
Of course there is.
> Usenet posts show up when they show up. That will be a different time
> and order for different people.
That's true, but unless your newsserver delayed my post more than 1.5h,
it's not relevant, is it?
> If you are refering to your post where you propose switching from the
> original n*n+k algorithm to a k*n algorithm, I don't recall whether I read
> it before or after I suggested going with a n+k algorithm which I consider
> to be simpler as well as more scalable.
That did surprise me. This was the solution I had suggested:
for (1..3) { print splice(@files, rand @files, 1), "\n" }
> So even if I did read your post
> first, I still thought my opinion was worth stating.
I didn't mean to say anything else. My apologies if I gave you another
impression.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 20 Jan 2006 03:08:00 GMT
From: "Nospam" <nospam@home.com>
Subject: soap::lite for activeperl 5.8
Message-Id: <kuYzf.1276$OI3.23@newsfe2-win.ntli.net>
where can I download this module?
------------------------------
Date: Fri, 20 Jan 2006 14:44:25 +1100
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: soap::lite for activeperl 5.8
Message-Id: <43d05d06$0$16851$afc38c87@news.optusnet.com.au>
"Nospam" <nospam@home.com> wrote in message
news:kuYzf.1276$OI3.23@newsfe2-win.ntli.net...
> where can I download this module?
>
>
ppm install http://theoryx5.uwinnipeg.ca/ppms/SOAP-Lite.ppd
Cheers,
Rob
------------------------------
Date: Thu, 19 Jan 2006 20:10:03 -0800
From: "Mark" <nospam@thanksanyway.org>
Subject: Trouble using LIB.PM to modify @INC
Message-Id: <yM2dnZPqbNoH_03eRVn-hA@w-link.net>
Hello.
My web site recently began spitting out a stream of errors to the error log:
[Thu Jan 19 19:10:40 2006] gen_page.pm: Use of uninitialized value in hash
element at /usr/lib/perl/5.8/lib.pm line 59.
[Thu Jan 19 19:10:40 2006] jpg.pm: Use of uninitialized value in hash
element at /usr/lib/perl/5.8/lib.pm line 59.
For some reason, the LIB module is unhappy with me. It breaks on the
following line:
@INC = grep { ++$names{$_} == 1 } @INC;
I have tried several variations of the statement that passes my private
module path to the LIB module:
use lib "/home/username/sitename.com/cgi-bin";
use lib q(/home/username/sitename.com/cgi-bin);
use lib qq(/home/username/sitename.com/cgi-bin);
All result in the same error.
Any suggestions?
Thanks
-Mark
------------------------------
Date: Thu, 19 Jan 2006 21:59:57 -0800
From: "Mark" <nospam@thanksanyway.org>
Subject: Re: Trouble using LIB.PM to modify @INC
Message-Id: <ZumdnSOSVMHD4U3enZ2dnUVZ_smdnZ2d@w-link.net>
I think I have solved it. The cause looks totally unrelated,
but weirdness does tend to propogate and change form
in Perl. That's why I love it so.
-Mark
------------------------------
Date: Fri, 20 Jan 2006 05:47:45 -0500
From: "Daniel Kaplan" <NoSPam@NoSpam.com>
Subject: Using RegExp to locate a part of scalar
Message-Id: <1137754065.617668@nntp.acecape.com>
Hi All,
Am sure that it's in the faq, just can't find it, but how can I use RegExp
to locate a piece of a scalar that is encompassed by particular text?
For instance, let's say I have a scalar $foo and it contains:
name="john doe" age="31" dob="12/22/1964"
I want to grab only the text that is in between age=" and "
I am sure that this is called something, and that there is a way to do this.
If anyone could provide me with the linkin the fact, or what this would be
called I woudl appreciate it.
THanks
------------------------------
Date: Fri, 20 Jan 2006 08:45:06 GMT
From: Lars Haugseth <njus@larshaugseth.com>
Subject: Re: Validating massive amounts of external links
Message-Id: <87y81b47rc.fsf@onyxia.eiendomsnett.no>
* "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid> wrote:
|
| Lars Haugseth wrote:
|> I have a database with a table containing (among others) the columns
|> URL, STATUS and LASTCHECKED. Stored in the table are thousand of records
|> containg links to external resources (all using the HTTP protocol.)
|
| Randal has an article about checking bookmarked links, which might help:
|
| http://www.stonehenge.com/merlyn/UnixReview/col56.html
Lovely. This is something I should be able to use as a basis.
Many thanks to you all for the hints.
--
Lars Haugseth
"If anyone disagrees with anything I say, I am quite prepared not only to
retract it, but also to deny under oath that I ever said it." -Tom Lehrer
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 8870
***************************************
