[31444] in Perl-Users-Digest
Perl-Users Digest, Issue: 2696 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Nov 27 06:09:37 2009
Date: Fri, 27 Nov 2009 03:09:05 -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, 27 Nov 2009 Volume: 11 Number: 2696
Today's topics:
DLL unload question for embedded Perl on Windows <u8526505@gmail.com>
Re: Good Golly Miss Molly Perl. Been so long. <ben@morrow.me.uk>
Re: Good Golly Miss Molly Perl. Been so long. <RedGrittyBrick@spamweary.invalid>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Quick CGI question (specific to the CGI package) <r.ted.byers@gmail.com>
Re: Quick CGI question (specific to the CGI package) <r.ted.byers@gmail.com>
Re: Quick CGI question (specific to the CGI package) <ben@morrow.me.uk>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 27 Nov 2009 02:46:30 -0800 (PST)
From: cyl <u8526505@gmail.com>
Subject: DLL unload question for embedded Perl on Windows
Message-Id: <d3e1af17-c31f-4ff7-af3e-48e27d65050c@y32g2000prd.googlegroups.com>
I ran into some problems when executing the sample code from perldoc
about embedding Perl in a C program. Here are my codes
---- embeddedperl.c begin ----
#include <EXTERN.h> /* from the Perl distribution */
#include <perl.h> /* from the Perl distribution */
EXTERN_C void boot_DynaLoader (pTHX_ CV* cv);
EXTERN_C void xs_init(pTHX)
{
char *file = __FILE__;
/* DynaLoader is a special case */
newXS("DynaLoader::boot_DynaLoader", boot_DynaLoader, file);
}
void runperl()
{
int ARGC = 2;
char *ARGV[]={"","test.pl"};
PerlInterpreter *my_perl;
PERL_SYS_INIT3(&ARGC,(char ***)&ARGV,NULL);
my_perl = perl_alloc();
perl_construct(my_perl);
PL_exit_flags |= PERL_EXIT_DESTRUCT_END;
perl_parse(my_perl, xs_init, ARGC, ARGV, (char **)NULL);
perl_run(my_perl);
perl_destruct(my_perl);
perl_free(my_perl);
PERL_SYS_TERM();
}
int main(int argc, char **argv, char **env)
{
int i=0;
for (i=0;i<2;i++)
runperl();
}
---- embeddedperl.c end ----
---- test.pl begin ----
use Cwd;
print cwd,"\n";
---- test.pl end ----
Here are the problems I got during execution
1. The loaded DLLs do not unload after the Perl interpreter is
shutdown
In my example, after perl_parse() Cwd.dll will be loaded. I
expected this dll will be unloaded after calling
perl_run() but it was not. How do I force all DLLs to be unloaded
after a script finishes?
2. perl_destruct() always throws exception. I have to comment out it
for my program to run. I suspect if it can run
without problem, maybe my 1st question can be solved.
3. After commenting out perl_destruct(), my program throws exception
after calling runperl() the 2nd time. It
actually died on perl_parse(). Since I wrap everything in a sub-
routine runperl() I thought everything starts from
scratch. However It seems not. I have no idea how come it is OK
the 1st time but not the 2nd.
Hope somebody can shed light on these. Thanks very much.
------------------------------
Date: Thu, 26 Nov 2009 19:03:47 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Good Golly Miss Molly Perl. Been so long.
Message-Id: <j103u6-9q9.ln1@osiris.mauzo.dyndns.org>
[please don't send email CCs of newsgroup posts]
Quoth "Adam Russell" <ac.russell@live.com>:
>
> "Ben Morrow" <ben@morrow.me.uk> wrote in message
> news:b7s0u6-oef2.ln1@osiris.mauzo.dyndns.org...
> >
> > Quoth Adam Russell <ac.russell@live.com>:
> >> No, but there is a perl port to the SymbianOS.
> >> I have made some contributions to it so I can say
> >> that it is currently in a working state provided you
> >> configure a Symbian development environment.
> >
> > Really? Last time I looked at perl/S60 it was nominally functional, but
> > practically useless, and I assumed that since Jarkko'd stopped working
> > on it the port was dead. Are there any sane interfaces to the native S60
> > APIs, like PyS60 has?
> That is what I am currently working on...giving a perl
> face to S60. There are two of us mainly, me and Osvaldo Villalon. We
> had quite a bit of work to just getting Jarkko's work cohesive with
> current sources.
> We work on this as our time allows. You know the deal:
> this is an all volunteer effort etc etc
> Between work, grad school, home life, yeah, I get to it
> when I can. :)
I understand that. I was certainly not intending to disparage your work,
or others', so if what I said came across that way I apologise.
> Anyway, I take objection to your negativity. This is the
> sort of thing that pesters what should be a happy open source community.
> What I wish you would have said is:
> "Really? I am jealous of the S60 functionality the
> python guys have. Where are you in development of this and can you give
> us
> a road map to where you want to go in terms of allowing a richer set
> of APIs? What can interested parties do to help?"
> I have answers to these questions but, sadly, you didn't
> ask. Did you?
Assume I did.
Ben
------------------------------
Date: Fri, 27 Nov 2009 09:44:09 +0000
From: RedGrittyBrick <RedGrittyBrick@spamweary.invalid>
Subject: Re: Good Golly Miss Molly Perl. Been so long.
Message-Id: <4b0f9f6c$0$2534$da0feed9@news.zen.co.uk>
Shmuel (Seymour J.) Metz wrote:
> In <878wdupl9n.fsf@quad.sysarch.com>, on 11/25/2009
> at 12:27 PM, "Uri Guttman" <uri@StemSystems.com> said:
>
>> because it sucked to begin with. learn how to code without gotos.
>
> There's nothing wrong with goto when used properly. Like any tool, it can
> be and often is misused, but it's useful in its place.
>
I've never found a situation where I thought it would be useful to use
goto. When modifying other people's code that contains gotos it has
almost invariably made my job harder. Much harder.
I'm sure gotos can be used well, its just that I've never encountered a
good use of goto in the code I've had to grapple with in thirty years of
software development.
Clearly other people's experience differs.
--
RGB
------------------------------
Date: Fri, 27 Nov 2009 02:13:04 -0600
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <IsednZmrNbqNF5LWnZ2dnUVZ_sidnZ2d@giganews.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Thu, 26 Nov 2009 11:13:12 -0800 (PST)
From: Ted Byers <r.ted.byers@gmail.com>
Subject: Re: Quick CGI question (specific to the CGI package)
Message-Id: <5c8a124b-667f-4672-add7-91f398949e51@x16g2000vbk.googlegroups.com>
On Nov 26, 12:40=A0pm, Ted Byers <r.ted.by...@gmail.com> wrote:
> On Nov 26, 11:49=A0am, Sherm Pendley <spamt...@shermpendley.com> wrote:
>
> > Ted Byers <r.ted.by...@gmail.com> writes:
> > > problem remains for the asf and avi files. =A0For asf files I tried
> > > video/asf and video/x-ms-asf, and for avi files I tried video/avi,
> > > video/msvideo and video/x-msvideo' all to no avail.
>
> > There's no need to guess - just look at Apache's mime.types file to see
> > what MIME type it maps to a given filename extension. The relevant line=
s
> > from my local copy of that file are:
>
> > =A0 =A0 video/x-msvideo =A0 =A0 =A0avi
> > =A0 =A0 video/x-ms-asf =A0 =A0 =A0 =A0asf asx
>
> > sherm--
>
> OK, On mine, there is a line like your's for avi files, but there is
> nothing in the mime.types file on my system for asf files. =A0This is
> puzzling since everything works well if I just redirect to an asf file
> in htdocs instead of setting the content type and then writing the
> content of the file to standard out in binary mode.
>
> But that doesn't cover what is happening on the client side. =A0Even
> though the server may not send video/avi as the MIME type for an avi
> file, both Firefox and MS IE recognize video/avi. =A0I know this because
> Mumia's latest example worked fine even though he set the content type
> to video/avi. =A0That give's me an idea, from what you said and what
> Mumia's example does, that I will have to test after lunch.
>
> Cheers,
>
> Ted
OK, final result: the idea that I got just before lunch, from
combining what Mumia provided and what sherm said paid off, and now
everything works as expected. And I even improved performance by
modifying Mumia's example to use sysread and syswrite.
There are still aspects of the behaviour I saw previously that I don't
understand. For example, once I used video/mpeg as the content type
(not using Mumia's example) the client believed the file name was
'my.cgi.script.cgi.mpg' and knew enough to try to open it using
Windows Media Player, but with all the other content types, the same
client believed the file name was'my.cgi.script.cgi'. Why the
difference? Anyway, although I am not happy with this gap in my
understanding, I can proceed to the next step.
When I applied Mumia's example to my own code, in each case, whether I
was sending an asf file, an avi file or an mpg file, in every case the
client believed the file name was what was actually the correct file
name for the clip being sent, and as a result, in each case the file
was displayed correctly using Windows Media Player.
Thanks all.
Ted
------------------------------
Date: Thu, 26 Nov 2009 13:04:10 -0800 (PST)
From: Ted Byers <r.ted.byers@gmail.com>
Subject: Re: Quick CGI question (specific to the CGI package)
Message-Id: <d05c018b-d250-4bfa-9f8d-e3d4495ae61c@r31g2000vbi.googlegroups.com>
On Nov 26, 2:06=A0pm, "Jochen Lehmeier" <OJZGSRPBZ...@spammotel.com>
wrote:
> On Wed, 25 Nov 2009 23:57:06 +0100, Ted Byers <r.ted.by...@gmail.com> =A0
> wrote:
>
> > In my testing, the client browser thinks
> > the video file content has the cgi script as the file name.
>
> Of course, the URL ishttp://host/cgi-bin/script.plor something like =A0
> that. The browser thinks the file is called "script.pl".
>
I can understand that. What isn't clear is why either the client or
the server is changing that to script.pl.mpg when an mpeg is requested
and not when the files with other video formats are requested (even
avi and there is a line in mime.types saying what the mime type is for
avi files).
> An easy way to change this is to use the URL =A0http://host/cgi-bin/scrip=
t.pl/file.avi(or whatever file name you want to =A0
> have). Apache will know to actually call your script.pl, and not try to =
=A0
> access script.pl as a directory.
Oh. OK.
The only issue with that solution is that I won't know until run time
what format the requested clip is actually in.
Thanks
Ted
------------------------------
Date: Thu, 26 Nov 2009 21:31:31 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Quick CGI question (specific to the CGI package)
Message-Id: <jm83u6-ufd.ln1@osiris.mauzo.dyndns.org>
Quoth Ted Byers <r.ted.byers@gmail.com>:
> On Nov 26, 2:06 pm, "Jochen Lehmeier" <OJZGSRPBZ...@spammotel.com>
> wrote:
> > On Wed, 25 Nov 2009 23:57:06 +0100, Ted Byers <r.ted.by...@gmail.com>
> > wrote:
> >
> > > In my testing, the client browser thinks
> > > the video file content has the cgi script as the file name.
> >
> > Of course, the URL ishttp://host/cgi-bin/script.plor something like
> > that. The browser thinks the file is called "script.pl".
>
> I can understand that. What isn't clear is why either the client or
> the server is changing that to script.pl.mpg when an mpeg is requested
> and not when the files with other video formats are requested (even
> avi and there is a line in mime.types saying what the mime type is for
> avi files).
This has not been a Perl problem for some time now. The question of what
the browser does with the filename is entirely at the discretion of the
browser. You may find that the different types are configured
differently in some way in the browser's MIME settings, or are being
picked up by different plugins. The mime.types file on the server has no
effect here: all that does is map extensions to content types for files
served directly (as opposed to through a CGI script) by the server.
> > An easy way to change this is to use the URL
> http://host/cgi-bin/script.pl/file.avi(or whatever file name you want
> to
> > have). Apache will know to actually call your script.pl, and not try to
> > access script.pl as a directory.
>
> Oh. OK.
>
> The only issue with that solution is that I won't know until run time
> what format the requested clip is actually in.
<shrug> Then simply send the appropriate content-type, and tell people
with broken browsers that think URLs have file extensions to get rid of
them :).
Ben
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 2696
***************************************
