[29693] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 937 Volume: 11

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Oct 15 14:09:45 2007

Date: Mon, 15 Oct 2007 11:09:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)

Perl-Users Digest           Mon, 15 Oct 2007     Volume: 11 Number: 937

Today's topics:
    Re: a nice little perl utility <bik.mido@tiscalinet.it>
    Re: a nice little perl utility <bik.mido@tiscalinet.it>
    Re: a nice little perl utility <rkb@i.frys.com>
    Re: a nice little perl utility <rkb@i.frys.com>
    Re: a nice little perl utility <bik.mido@tiscalinet.it>
        ACM SIGAPL / APL2007 Conference / Montreal / one week a <mkent@acm.org>
        Auction Software <swasaaron@gmail.com>
    Re: Parsing of undecoded UTF-16 error <paduille.4061.mumia.w+nospam@earthlink.net>
    Re: Strong Blog CGI in Perl <izidoor@invalid.com>
    Re: Strong Blog CGI in Perl <siliconchaos@gmail.com>
    Re: Strong Blog CGI in Perl <izidoor@invalid.com>
    Re: Strong Blog CGI in Perl <izidoor@invalid.com>
    Re: Strong Blog CGI in Perl <bik.mido@tiscalinet.it>
    Re: UTF8 strings and filesystem access (Gary E. Ansok)
    Re: Windows,ASSOC,FTYPE,.pl,.plx,.sh <rkb@i.frys.com>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

----------------------------------------------------------------------

Date: Mon, 15 Oct 2007 14:29:46 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: a nice little perl utility
Message-Id: <tjl6h39rj0099ca6klip5uqh2d3g907poj@4ax.com>

On Sat, 13 Oct 2007 17:12:16 -0700, "Wade Ward" <zaxfuuq@invalid.net>
wrote:

>I no longer do.  I tried to use the komodo IDE but couldn't get anything off 
>the ground as a beginner.  It was a huge waste of time for me.  Not that the 
>product is necessarily bad; I'm just nowhere near where I can use something 
>like that yet.

Count me for another one who is nowhere near "where" he can use
something like that. And I don't particularly regret it!  ;)

>I finally got my head around this and came up with another example:
>http://www.zaxfuuq.net/perl7.htm

Please, *please*, don't! What is the point of posting links to
screenshots (with the additional hassle for you to create and upload
them and for us to switch media to see them) when (i) it is not
necessary, (ii) being them about some pure text item it would be
easier and more communication-friendly to just paste it here directly?

I suggest you to go to DOS console's properties and enable fast
editing mode. Then dragging the mouse with left button pressed will
select, pressing return copy and right-clicking paste. This makes its
c&p somewhat more starnixish, although I still can't make sense of the
additional key required in the middle. M$teries! Another slight
difference is that it is rectangle basis, which is also annoying
sometimes.

Back to Perl -but not too much, really- your screenshot shows your
attempts to call a script. Note that you can do so with any of the
following:

  perl script.pl [arguments]
  script.pl [arguments]

In the former the extension need not be .pl and the latter assumes
that .pl has been associated with Perl, which ActivePerl's
installation automatically does - and I'm 99% confident you're using
AP. If you additionally add .pl to the %PATHEXT% env variable (which
AP's installation does *not* do), then you would be able to call the
script without specifying its extension. That is, if you have
script.pl you could also call it like

  script [arguments]

Last, and on a very x 10 OT basis (already waiting for Ben to bash
me!) I seem to notice a "spurious" line on the left side of your last
screenshot. This suggests me that you're grabbin the whole screen with
PrtSc and cropping it with some image editing program - one more
reason to be astonished by your byzantine way of proceeding. But you
can just grab the window of a specific app in the first place, by
putting it in foreground and pressing Alt-PrtSc instead.


HTH,
Michele
-- 
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
 .'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,


------------------------------

Date: Mon, 15 Oct 2007 14:31:04 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: a nice little perl utility
Message-Id: <van6h3l5isudce2eh4m50c8agfqr1vpfnq@4ax.com>

On Sun, 14 Oct 2007 09:27:08 -0700, Cloink
<Cloink_Friggson@ntlworld.com> wrote:

>Um, I thought I'd better be a good boy and add the shebang as written
>here (I'm on Windows), but it stopped my cgi-script working.
>Eventually, I tracked down an error in my Apache error.log saying
>
>"[Sun Oct 14 17:15:26 2007] [error] [client 127.0.0.1] (OS 3)The
>system cannot find the path specified.  : couldn't create child
>process: 720003: xx.pl, referer: http://[etc]"

An entirely different problem. Since the OS cannot do it, the
webserver takes care of doing it. In that case it *does* want the
correct path.


Michele
-- 
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
 .'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,


------------------------------

Date: Mon, 15 Oct 2007 15:38:37 -0000
From:  Ron Bergin <rkb@i.frys.com>
Subject: Re: a nice little perl utility
Message-Id: <1192462717.300629.34320@e9g2000prf.googlegroups.com>

On Oct 15, 5:31 am, Michele Dondi <bik.m...@tiscalinet.it> wrote:
> On Sun, 14 Oct 2007 09:27:08 -0700, Cloink
>
> <Cloink_Frigg...@ntlworld.com> wrote:
> >Um, I thought I'd better be a good boy and add the shebang as written
> >here (I'm on Windows), but it stopped my cgi-script working.
> >Eventually, I tracked down an error in my Apache error.log saying
>
> >"[Sun Oct 14 17:15:26 2007] [error] [client 127.0.0.1] (OS 3)The
> >system cannot find the path specified.  : couldn't create child
> >process: 720003: xx.pl, referer:http://[etc]"
>
> An entirely different problem. Since the OS cannot do it, the
> webserver takes care of doing it. In that case it *does* want the
> correct path.
>
> Michele
> --

Apache on Windows does not require the correct path in the shebang
line, as long as apache is configured "correctly".

Uncomment the following line in the httpd.conf file and it will use
the registry instead of the shebang line to find Perl.

ScriptInterpreterSource registry

Once that is "activated", you can use the exact same shebang line as
you use on *nix.



------------------------------

Date: Mon, 15 Oct 2007 16:00:09 -0000
From:  Ron Bergin <rkb@i.frys.com>
Subject: Re: a nice little perl utility
Message-Id: <1192464009.675809.144480@e9g2000prf.googlegroups.com>

On Oct 15, 8:38 am, Ron Bergin <r...@i.frys.com> wrote:
>
> Apache on Windows does not require the correct path in the shebang
> line, as long as apache is configured "correctly".
>
> Uncomment the following line in the httpd.conf file and it will use
> the registry instead of the shebang line to find Perl.
>
> ScriptInterpreterSource registry
>
> Once that is "activated", you can use the exact same shebang line as
> you use on *nix.

In addition to "activating" that line in the conf file, you could also
make a registry entry that assures that Perl will run all .cgi scripts
(without having to have a file type association) and will run in taint
mode.

Create and execute a cgi.reg file with the following:

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.cgi]
[HKEY_CLASSES_ROOT\.cgi\Shell]
[HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI]
[HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command]
@="C:\\Perl\\bin\\perl.exe -T"




------------------------------

Date: Mon, 15 Oct 2007 18:38:19 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: a nice little perl utility
Message-Id: <1r57h3th4nn1jvko1chktcfh3gnah5lmpc@4ax.com>

On Mon, 15 Oct 2007 15:38:37 -0000, Ron Bergin <rkb@i.frys.com> wrote:

>> An entirely different problem. Since the OS cannot do it, the
>> webserver takes care of doing it. In that case it *does* want the
>> correct path.
>>
>> Michele
>> --
>
>Apache on Windows does not require the correct path in the shebang
>line, as long as apache is configured "correctly".
>
>Uncomment the following line in the httpd.conf file and it will use
>the registry instead of the shebang line to find Perl.
>
>ScriptInterpreterSource registry
>
>Once that is "activated", you can use the exact same shebang line as
>you use on *nix.

Thank you for the correction. Of course I didn't know and was just
guessing instead.


Michele
-- 
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
 .'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,


------------------------------

Date: Mon, 15 Oct 2007 05:22:33 -0400
From: Mike Kent <mkent@acm.org>
Subject: ACM SIGAPL / APL2007 Conference / Montreal / one week away
Message-Id: <47133159.9010204@acm.org>

Conference page
	// with links to program details //
		(updated Friday 10/12)

	http://www.sigapl.org/apl2007.html


Co-located with OOPSLA 2007

	http://www.oopsla.org/oopsla2007


On-line registration (through Wednesday 10/17)

	http://www.regmaster.com/conf/oopsla2007.html
	


------------------------------

Date: Mon, 15 Oct 2007 12:28:37 -0000
From:  Aaron <swasaaron@gmail.com>
Subject: Auction Software
Message-Id: <1192451317.645038.261740@y27g2000pre.googlegroups.com>

 AJ Auction Pro is a feature packed software that provides a trusted
buying or selling environment. It provides full fledged auction
software solutions for the demanding auction sites. It is a real time
auction software that best caters to the needs of our emerging and
existing clients. It leads to a successful and profitable auction
business. Your customers would never miss a single opportunity to buy
or sell.Start your own profitable Auction Portal today.

http://www.ajauctionpro.com/about_ajauction_pro.php



------------------------------

Date: Mon, 15 Oct 2007 02:16:34 -0500
From: "Mumia W." <paduille.4061.mumia.w+nospam@earthlink.net>
Subject: Re: Parsing of undecoded UTF-16 error
Message-Id: <13h65961ka9fb2d@corp.supernews.com>

On 10/15/2007 01:02 AM, livefreeordie wrote:
> Hi - I'm using the following construct to parse an HTML page:
> 
> use HTTP::Request;
> use LWP::UserAgent;
> 
> my $req = new HTTP::Request(GET=>$url);
> my $ua  = new LWP::UserAgent();
> my $resp = $ua->request($req);
> my $content = $resp->decoded_content();
> 
> I'm getting the following error when attempting to access this URL:
> 
> Error: Parsing of undecoded UTF-16 at C:/Perl/lib/LWP/Protocol.pm line
> 116.
> URL:  http://securities.stanford.edu/1009/RICKEL96/'
> 

I don't get this with LWP::UserAgent 2.033 and HTTP::Request 1.40.

> When I take a look at the content, each character is separated by a
> newline or space.
> 

The characters are separated by nulls. The file is in UTF16LE format; 
however, this is not advertised in the HTTP header.


> What is this, and how can I get around it?  I've retrieved other pages
> successfully.
> 
> Jamie
> 

What version of Perl are you using? What module versions are you using?


------------------------------

Date: Mon, 15 Oct 2007 13:04:10 +0200
From: Izidoor <izidoor@invalid.com>
Subject: Re: Strong Blog CGI in Perl
Message-Id: <MPG.217d6791cf9f9f7d989964@news.tiscali.fr>

In article <87sl4dl3u0.fsf@mithril.chromatico.net>, 
cwilbur@chromatico.net says...
> Er, LiveJournal and MovableType don't have "the usual features"?
> 
> There's also Blosxom, which I'm not familiar with.
> 
> Charlton
> 

Thank you Charlton. 

No, the one I've seen are not those. For example, I've tried MyBlog from 
http://www.fuzzymonkey.net/software/blog/. So, it seems I have to visit 
your list. 

Do you know about a commented directory on this subject (blog script in 
Perl) ? What are the advantages and drawbacks of the 3 (or 4) you 
indicate me ?


------------------------------

Date: Mon, 15 Oct 2007 06:14:31 -0700
From:  siliconchaos <siliconchaos@gmail.com>
Subject: Re: Strong Blog CGI in Perl
Message-Id: <1192454071.257283.234630@v23g2000prn.googlegroups.com>

On Oct 14, 2:10 pm, Izidoor <izid...@invalid.com> wrote:
> Hello everybody. Do you know about a strong CGI written in Perl to
> manage a blog ?
>
> Looking around, I've seen a lot in PHP/MySQL or even without MySQL, but
> nothing in Perl. Or, more precisely, the some I've seen in Perl doesn't
> show the usual features like list of recent comments, calendar to browse
> the archives, easy configuration, etc.

You might want to try AngerWhale [http://www.angerwhale.org/] for an
interesting approach at blogging software. Jonathan Rockway's  site
[http://www.jrocks.us] has some good slides on the software.

And of course you can also try slashcode [http://www.slashcode.com/,
http://sourceforge.net/projects/slashcode/] which as you can probably
guess from the name is the software running slashdot [http://
www.slashdot.org]

Regards,

Robert



------------------------------

Date: Mon, 15 Oct 2007 15:14:29 +0200
From: Izidoor <izidoor@invalid.com>
Subject: Re: Strong Blog CGI in Perl
Message-Id: <MPG.217d861ec2526d9c989965@news.tiscali.fr>

In article <87sl4dl3u0.fsf@mithril.chromatico.net>, 
cwilbur@chromatico.net says...
> >>>>> "I" == Izidoor  <izidoor@invalid.com> writes:
> 
>     I> Looking around, I've seen a lot in PHP/MySQL or even without
>     I> MySQL, but nothing in Perl. Or, more precisely, the some I've
>     I> seen in Perl doesn't show the usual features like list of
>     I> recent comments, calendar to browse the archives, easy
>     I> configuration, etc.
> 
> Er, LiveJournal and MovableType don't have "the usual features"?
> 
> There's also Blosxom, which I'm not familiar with.
> 
> Charlton
> 
> 
> 

I've seen the name you gave me :

- Er : don't know where to find it !

- LiveJournal at http://www.livejournal.com/ : it seems to be a blog 
host, not a software to install on your own cgi-bin space.

- MovableType : http://www.movabletype.com/download/personal-use.html : 
it's effectively a Perl script using a SQL database, but don't know 
really yet why they ask for PHP (they say for "dynamic publishing", but 
I've not read the detail at this time).

- Blosxom : http://www.blosxom.com/ : also a Perl script, lightweight 
and open-source, and it doesn't need any database server. I don't know 
if it accepts image upload ?!

So, I have to look deeper MovableType and Blosxom (and Er maybe), but 
here is the list of feature I wish :

- Upload of text and image
- Permalink 
- RSS feed
- Archives navigation
- Searching
- List of links toward articles containing the most recent comments

And, without use of any external database could be a plus for my case.


------------------------------

Date: Mon, 15 Oct 2007 17:45:47 +0200
From: Izidoor <izidoor@invalid.com>
Subject: Re: Strong Blog CGI in Perl
Message-Id: <MPG.217da99a7f403069989966@news.tiscali.fr>

In article <1192454071.257283.234630@v23g2000prn.googlegroups.com>, 
siliconchaos@gmail.com says...
> On Oct 14, 2:10 pm, Izidoor <izid...@invalid.com> wrote:
> > Hello everybody. Do you know about a strong CGI written in Perl to
> > manage a blog ?
> >
> > Looking around, I've seen a lot in PHP/MySQL or even without MySQL, but
> > nothing in Perl. Or, more precisely, the some I've seen in Perl doesn't
> > show the usual features like list of recent comments, calendar to browse
> > the archives, easy configuration, etc.
> 
> You might want to try AngerWhale [http://www.angerwhale.org/] for an
> interesting approach at blogging software. Jonathan Rockway's  site
> [http://www.jrocks.us] has some good slides on the software.
> 
> And of course you can also try slashcode [http://www.slashcode.com/,
> http://sourceforge.net/projects/slashcode/] which as you can probably
> guess from the name is the software running slashdot [http://
> www.slashdot.org]
> 
> Regards,
> 
> Robert
> 
> 

Thank you, Robert. I've added them to my list *TO_TEST*.

So, actually, my list is this one (from Charlton post too) : 

- MovableType 
- Blosxom 
- AngerWhale 
- slashcode 

At your opinion, what's the easier (about install and configuration) to 
build a blog with these features ? :

- Ability to fine tune the theme (at least, colors and fonts)
- Easy web admin board (to post, edit, delete, etc)
- Text posting (and ability to edit it in case of mistake)
- Image uploading (will appear as zoomable thumbnail in post)
- Permalink (to display both one post and its comments in one page)
- RSS feed (to allow syndication)
- Archives navigation (through category or date)
- Searching (word based with eventual OR/AND logic)
- List of links toward articles containing the most recent comments
- Ability to work in an iframe (don't know what it will do about iframe 
height ; does it will resize automatically)
- Not any need of external database server (MySQL, etc) ; I hesitate on 
this point.

And it would be a plus if :
- Choice of a category
- Comment posting w/o subscription, but saving coordinates in a cookie
- Good comment preview
- Unicode support (to accept chars like 'euro' or capitals w/ accent)
- Plugin oriented (just in case a feature doesn't exist)
- Possibility to bann a user, IP or domain
- Good errors management (I mean toward user wiyh explicit message)
- Sending of every post toward its author (and me through BCC)


------------------------------

Date: Mon, 15 Oct 2007 18:44:02 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Strong Blog CGI in Perl
Message-Id: <8367h31vs88dhdl3h1pqkninnkqnadbi6l@4ax.com>

On Mon, 15 Oct 2007 17:45:47 +0200, Izidoor <izidoor@invalid.com>
wrote:

>- Searching (word based with eventual OR/AND logic)
                              ^^^^^^^^
                              ^^^^^^^^

<ot>
I suppose you're not a native English speaker and ITYM "possible"
there.
</ot>


Michele
-- 
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
 .'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,


------------------------------

Date: Mon, 15 Oct 2007 17:03:25 +0000 (UTC)
From: ansok@alumni.caltech.edu (Gary E. Ansok)
Subject: Re: UTF8 strings and filesystem access
Message-Id: <ff06gt$m11$1@naig.caltech.edu>

In article <slrnfh46l5.6q4.hjp-usenet2@zeno.hjp.at>,
Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
>On 2007-10-11 22:22, Gary E. Ansok <ansok@alumni.caltech.edu> wrote:
>> In article <slrnfgt1r0.o12.hjp-usenet2@zeno.hjp.at>,
>> Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
>>>> Quoth ansok@alumni.caltech.edu (Gary E. Ansok):
>>>>> 
>>>>>   1)  $dir is encoded internally in UTF8 (even if $dir doesn't 
>>>>>            contain any non-ASCII characters)
>>>
>>>Then why is it a wide string?
>>
>> It's read in using XML::Simple from a config file that does not
>> contain any non-ASCII characters, or any encoding specification in
>> the XML prolog (though adding "encoding='ISO-8859-1'" didn't help).
>
>> Now that I've dug a little deeper, I think upgrading some of our
>> module versions may help avoid this problem -- a recent change to 
>> XML::LibXML mentioned "strip-off UTF8 flag for consistent behavior 
>> independent of document encoding".
>
>You omitted an important piece here: The entry reads 
>"strip-off UTF8 flag with $node->toString($format,1) for consistent ..."
>$node->toString returns a piece of XML, which always should be a series
>of bytes, not characters. I haven't looked at the source code of
>XML::Simple, but it probably uses $text->data or $node->nodeValue.

I've worked around the problem by switching from XML::LibXML to
XML::SAX::PurePerl as the underlying parser -- now, the string 
read in from the configuration file no longer has the UTF8 flag
set, and the problem does not appear.

I still think it's a bug that a string that can successfully opendir()
a directory, combined (including the appropriate separator) with a
file name read in by readdir(), does not result in a string that can
by used to open() or stat() the file.  Especially since the path appears
correct when printed as part of an error message, and it's difficult
to diagnose the problem without resorting to something like Devel::Peek.

Thanks for the assistance,
Gary Ansok


------------------------------

Date: Mon, 15 Oct 2007 16:58:01 -0000
From:  Ron Bergin <rkb@i.frys.com>
Subject: Re: Windows,ASSOC,FTYPE,.pl,.plx,.sh
Message-Id: <1192467481.691936.90820@e9g2000prf.googlegroups.com>

On Oct 11, 7:30 pm, "Jim Carlock" <anonym...@127.0.0.1> wrote:
> In setting up Perl within a Windows OS, what's the best way to
> configure Perl so that a Perl file can get run inside a cmd.exe
> prompt, but without using ASSOC or FTYPE to configure things.

Use the full path, i.e.,
C:\perl\bin\perl.exe myscript
>
> Once ASSOC and FTYPE are run, they configure HKLM inside the
> registry which in turn makes the whole operating system realize
> Perl is installed, and makes the operating system vulnerable to
> various exploits.

What exploits are you referring to and which of those do you believe
are "fixed" by not having a FTYPE or ASSOC?

>
> I hope to run a Perl application/script only inside a specific
> cmd.exe prompt, preferably one set up with a .cmd or .bat file,
> that in turn does not anyone viewing a website to run Perl. In
> other words, I seek to not allow the whole operating system to end
> up with the global updates that commands, ASSOC and FTYPE, employ.

So, you want to run a perl script, but you don't want it to run Perl.
That doesn't make any sense.

How is a person that is just viewing your website going to arbitrarily
run Perl?  They will only be able to run the cgi scripts that you
allow.  So, it sounds like the real vulnerability may be with your
poorly written cgi scripts.
>
> Does anyone know of a way to prevent ASSOC and FTYPE from making
> a change to the registry? Or perhaps of another way other than
> having to type in "Perl.exe printenv.pl"?
>
> --
> Jim Carlock

Setting the FTYPE, ASSOC, and PATH ENV are merely conveniences.
Removing them will not fix any real or perceived vulnerabilities.



------------------------------

Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin) 
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>


Administrivia:

#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc.  For subscription or unsubscription requests, send
#the single line:
#
#	subscribe perl-users
#or:
#	unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.  

NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice. 

To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.

#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.

#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.


------------------------------
End of Perl-Users Digest V11 Issue 937
**************************************


home help back first fref pref prev next nref lref last post