[9254] in Perl-Users-Digest
Perl-Users Digest, Issue: 2849 Volume: 8
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Jun 11 20:07:48 1998
Date: Thu, 11 Jun 98 17:01:40 -0700
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Thu, 11 Jun 1998 Volume: 8 Number: 2849
Today's topics:
Re: MODERATION: Time to Vote (Craig Berry)
Re: MODERATION: Time to Vote (John Stanley)
Re: Newbie question - password redirection script <rootbeer@teleport.com>
Re: Opening Files <angst@scrye.com>
Re: pack/unpack seps (Gary M. Greenberg)
Re: pass the gravy and the hashref, please -- solved (Mark-Jason Dominus)
Re: PASV <dolske@cis.ohio-state.edu>
Re: Performance impact of "require" <rootbeer@teleport.com>
Re: Perl and Netware and Linux. . .oh my!! <stevem@pacific.ddns.org>
Re: perl math accuracy <probavm@cat.com>
Re: perl math accuracy <rootbeer@teleport.com>
Re: perl math accuracy (Craig Berry)
Re: perl math accuracy <tchrist@mox.perl.com>
perl training? (Paula Burch)
Re: Please Help !!! <ebohlman@netcom.com>
Re: Prob in FAQ: Week of the year (Steffen Beyer)
Re: Prob in FAQ: Week of the year <tchrist@mox.perl.com>
Re: Stages in a pipeline <tchrist@mox.perl.com>
Starting a Dallas Perl Mongers group (Brand and Karina Hilton)
Re: Vote today, read CFV for c.l.p.moderated, Post the (Eric Eisenhart)
Digest Administrivia (Last modified: 8 Mar 97) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 11 Jun 1998 22:47:16 GMT
From: cberry@cinenet.net (Craig Berry)
Subject: Re: MODERATION: Time to Vote
Message-Id: <6lpmpl$qjr$1@marina.cinenet.net>
John Porter (jdporter@min.net) wrote:
: Craig Berry wrote:
: > Care to explain that?
:
: Aw, Craig, what'd ya have to go and do that for?
: John Stanley's eccentric railings have already filled
: volumes of clpm, and other ng's as well. No need to
: ask for yet more. DejaNews is our friend.
My apologies to all and sundry. I'd have cancelled my article had the
(many) email warnings reached me soon enough; alas, they did not.
I have avoided the entire 'debate' over moderation, resolving merely to
read the charter and vote when the opportunity arose. Thus, this thread
attracted my attention. I made the mistake of reading and responding to
an additional message on the thread without any knowledge of the
'backstory' involved.
Let's just think of this as one more argument for moderation and move on,
shall we?
---------------------------------------------------------------------
| Craig Berry - cberry@cinenet.net
--*-- Home Page: http://www.cinenet.net/users/cberry/home.html
| Member of The HTML Writers Guild: http://www.hwg.org/
"Every man and every woman is a star."
------------------------------
Date: 11 Jun 1998 23:15:12 GMT
From: stanley@skyking.OCE.ORST.EDU (John Stanley)
Subject: Re: MODERATION: Time to Vote
Message-Id: <6lpoe0$71b$1@news.NERO.NET>
In article <6lpmpl$qjr$1@marina.cinenet.net>,
Craig Berry <cberry@cinenet.net> wrote:
>My apologies to all and sundry. I'd have cancelled my article had the
>(many) email warnings reached me soon enough; alas, they did not.
It does my heart good to find yet another person who would rather let
other people tell him how to judge someone than judge for himself.
>I have avoided the entire 'debate' over moderation, resolving merely to
>read the charter and vote when the opportunity arose.
Unfortunately, by doing so, you miss all of the discussion about the
group, which might include some very good reasons to vote no. It might
not, but if you don't bother reading it, you won't find out until it is
too late.
>Let's just think of this as one more argument for moderation and move on,
>shall we?
Yes, silence is golden, etc.
------------------------------
Date: Thu, 11 Jun 1998 23:20:28 GMT
From: Tom Phoenix <rootbeer@teleport.com>
Subject: Re: Newbie question - password redirection script
Message-Id: <Pine.GSO.3.96.980611161937.5401r-100000@user2.teleport.com>
On Thu, 11 Jun 1998, Harley Jacoubsen wrote:
> Is it possible to just change the first line of the script
> $correctpass = "test";
> to something like
> $correctpass = "test","testing","tested";
You probably want to use a hash. An example of this sort of thing is in
the first chapter of the Llama book, as I recall. Hope this helps!
--
Tom Phoenix Perl Training and Hacking Esperanto
Randal Schwartz Case: http://www.rahul.net/jeffrey/ovs/
------------------------------
Date: 11 Jun 1998 23:22:56 GMT
From: angst <angst@scrye.com>
Subject: Re: Opening Files
Message-Id: <6lposg$k6n$1@jelerak.scrye.com>
F.Quednau <quednauf@nortel.co.uk> wrote:
: $dir = "/some/dir";
: opendir(CB, "$dir") || die "Cannot opendir:$!";
: foreach $file (sort readdir(CB)) {
: print "Current file is: $file\n";
: unless ($file eq "." || $file eq "..") {
: open (FILE, "< $dir/$file") || die "Strange, but true: $!";
: print "-- $file --\n";
: print <FILE>;
: close (FILE);
: }
: }
: closedir(CB);
: It took me 1 minute to answer your question, but almost 30 minutes to get the
: conditional right. I know, this is not a Perl question, but why are the
: following two conditionals not equivalent? Let me answer this myself...
Or you could have saved yourself a lot of time by using grep, eg:
foreach $file (sort (grep !/^\.\.?$/, readdir CB)){
etc.
But then, what you learned about logical conditionals in the process is
timeless, so maybe your method (or the headache you went through to get it to
work) is more valuable in the long run. And the brief explanation you gave
explaining the why will probably prove valuable to other readers of this group.
Also, if you want to do more than just open the file, and particularly
if you want to recurse directories, a construct such as the below might
be preferrable to continually appending directory names on to the filename:
foreach $file (sort (grep !/^\.\.?$/, map "$dir/$_", readdir CB)){
etc.
These examples are also in the Camel, although maybe not in this exact
syntax, since I couldn't immediately find them there (I just remember that they
were there), so just sort of made it up as I went along.
--
Erik Nielsen <eln@rmci.net>
mail to above (rather than header address) is answered significantly faster.
this post != views of anyone at all, really
"You are like...unix GOD" -- local tech support
------------------------------
Date: Thu, 11 Jun 1998 23:01:57 GMT
From: garyg@gator.net (Gary M. Greenberg)
Subject: Re: pack/unpack seps
Message-Id: <MPG.fea2b1f337ae6c1989683@news.gator.net>
[This followup was posted to comp.lang.perl.misc and a copy was sent to
the cited author.]
In article <6lneu3$518$2@csnews.cs.colorado.edu>, tchrist@mox.perl.com
says...
> I begin to wonder whether I have a teaching disability or
...
> $char = unpack("a", "\101");
> $byte = unpack("c", "\101");
>
> print "char is $char, byte is $byte\n";
>
> +-----------------------+
> | char is A, byte is 65 |
> +-----------------------+
>
> Please tell me this makes sense now. One gives you back a number in
> an 8-bit range, unsigned if "C" is used. The other gives you back a
> character string of length one.
>
> --tom
>
A very, very small nit:
I had to read this *twice* because the explanation for which is a string
vs. which is an optionally signed number in 8-bit range is reversed from
the order of declaration and result. And, I understood before I read the
posting ;-)
Cheers,
Gary # Perl Apprentice
-=- The C Programmers' Reference -=-
http://www.gator.net/~garyg/C/c.html
-=- Avenue Programmers' Classes' Requests -=-
http://www.gator.net/~garyg/class.htm
------------------------------
Date: 11 Jun 1998 19:07:16 -0400
From: mjd@op.net (Mark-Jason Dominus)
Subject: Re: pass the gravy and the hashref, please -- solved
Message-Id: <6lpnv4$51t$1@monet.op.net>
Keywords: bad fraud inflationary whole
In article <357DD139.F4835606@intes.net>,
Chris Winters <cwinters@intes.net> wrote:
>Okay, I figured this out. I'm breaking the original reference in the
>parent by doing a straight assignment:
>
>$self->{values} = $href;
Hey, what do you know? I guessed right.
------------------------------
Date: Thu, 11 Jun 1998 18:26:56 -0400
From: Justin Dolske <dolske@cis.ohio-state.edu>
Subject: Re: PASV
Message-Id: <Pine.SUN.3.95.980611182522.12247A-100000@snoopy.cis.ohio-state.edu>
On 11 Jun 1998, Tu-Thach wrote:
> print MYSOCK "PASV\r\n";
> print MYSOCK "RETR $filename\r\n";
> and the output prints "Entering Passive Mode (bunch of numbers)"
> and halts there forever. Am I doing something wrong?
Yes. I'd suggest reading RFC 959 and friends.
Justin Dolske <URL:http://www.cis.ohio-state.edu/~dolske/>
(dolske@cis.ohio-state.edu)
------------------------------
Date: Thu, 11 Jun 1998 23:09:28 GMT
From: Tom Phoenix <rootbeer@teleport.com>
Subject: Re: Performance impact of "require"
Message-Id: <Pine.GSO.3.96.980611145509.5401o-100000@user2.teleport.com>
On Thu, 11 Jun 1998 holgerman@my-dejanews.com wrote:
> To keep my code more managable, I group my subroutines in library files
> that I require at the beginning of the script (up to 15 files). I was
> wondering though what the performance impact on the script is as every
> external call (open, system, stat etc.) will negatively influence
> performance of the script (at least that's what I heard...).
Once a file has been require'd, it won't have to be loaded again. So,
calling 100 subroutines from a module takes about as long as calling 1
subroutine from a module and 99 from the main program. (There are some
other possibilities such as autoloading, but we can probably ignore that
here.) Is that what you were asking?
> Is there any rule of thumb to apply in this case (e.g. 'Do not require
> more than 20 files.')? Should I consolidate them into fewer files?
If you'd only want to use A with B and B with A, then it makes sense to
put them together. But there's nothing wrong with keeping them separate.
Hope this helps!
--
Tom Phoenix Perl Training and Hacking Esperanto
Randal Schwartz Case: http://www.rahul.net/jeffrey/ovs/
------------------------------
Date: Thu, 11 Jun 1998 22:36:15 +0000
From: Stephen Meyles <stevem@pacific.ddns.org>
To: Robert Eric Pearse <pearse@mail.shebang.net>
Subject: Re: Perl and Netware and Linux. . .oh my!!
Message-Id: <35805BDF.BD82D54@pacific.ddns.org>
I snipped this from a FAQ for a Perl app:
"Though MiniVend has ODBC capability, the Microsoft Access ODBC driver
is not a network driver. You cannot access it on a PC from your ISP or
UNIX system."
This being correct, you'll have to export you data from Access rather
than utilising ODBC.
Steve
Robert Eric Pearse wrote:
>
> Hey all,
>
> I've got what I "think" is a unique problem. . .
>
> Problem: There is constant stream of doc's piling up on a Netware
> networked drive. I need to put them on a colocated Linux web server.
> Also, there is an Access 2.0 database sitting on the same drive that
> contains data about the docs. (I know, I know. . .but the office is
> still using Win3.X. . .my hands are tied!)
>
> Here's what I need done:
> 1) Move the docs to the web server.
> 2) Grab the data in the Access database and shoot it over to a new
> database on the Linux box
> 3) Fix existing code to access the database for the docs and data
> instead of hunting in an ASCII file and some directories
>
> Yes, a job for Perl. No problem. Using Win32::ODBC to access the data.
> And 'readdir'ing my way all around that drive. (just getting silly with
> it. . .it is fun language).
>
> Here comes the Netware stuff (we're using it for printing and file
> sharing.) My Wintel box is acting as a "go between" between the network
> drive and the database. It just seems easier to format my hd and install
> Linux. (I'm prone to rash decisions. . .) But, how do I access the LAN.
> There must be someway to tie a Linux box into a Netware LAN to access
> printers, files, and that Access database.
>
> So, I think it breaks down to two problems:
>
> 1) How do I get access to printers and files on a Netware LAN from a
> Linux box?
> 2) How do access the Access database from Linux using Perl?
>
> From what little I know about ODBC, I gather that I need a DSN to Access
> the data. Can I put one on the Linux box? Also, I looked at a HOWTO on
> setting up an Intranet for Netware, etc. clients but I'm the client. It
> didn't help much.
>
> Cheers,
>
> Robert
--
"The biggest cause of trouble in the world today is that the stupid
people are
so sure about things and the intelligent folks are so full of doubts."
-- Bertrand Russell
------------------------------
Date: Thu, 11 Jun 1998 17:08:51 -0500
From: "Vincent M. Probasco" <probavm@cat.com>
Subject: Re: perl math accuracy
Message-Id: <35805573.92EC0424@cat.com>
Dave,
In general, it is a bad idea to compare floating point values.
You're better off checking to see if the
difference between the two floats is very small.
Vince
------------------------------
Date: Thu, 11 Jun 1998 23:21:32 GMT
From: Tom Phoenix <rootbeer@teleport.com>
Subject: Re: perl math accuracy
Message-Id: <Pine.GSO.3.96.980611162038.5401s-100000@user2.teleport.com>
On Thu, 11 Jun 1998, Dave Hutchins wrote:
> I can not find any reason why simple operations in perl return
> inaccurate results,
> such as (12 - 11.96) != 0.04
Maybe you can't find it because you're not looking in the FAQ. :-)
--
Tom Phoenix Perl Training and Hacking Esperanto
Randal Schwartz Case: http://www.rahul.net/jeffrey/ovs/
------------------------------
Date: 11 Jun 1998 23:28:48 GMT
From: cberry@cinenet.net (Craig Berry)
Subject: Re: perl math accuracy
Message-Id: <6lpp7g$qjr$2@marina.cinenet.net>
Vincent M. Probasco (probavm@cat.com) wrote:
: In general, it is a bad idea to compare floating point values.
: You're better off checking to see if the
: difference between the two floats is very small.
s/compare (floating point values)/test $1 for (in)equality/;
Relational comparsions (> >= < <=) are fine, and in fact are how you
impliment the "epsilon test" suggested.
---------------------------------------------------------------------
| Craig Berry - cberry@cinenet.net
--*-- Home Page: http://www.cinenet.net/users/cberry/home.html
| Member of The HTML Writers Guild: http://www.hwg.org/
"Every man and every woman is a star."
------------------------------
Date: 11 Jun 1998 23:29:31 GMT
From: Tom Christiansen <tchrist@mox.perl.com>
Subject: Re: perl math accuracy
Message-Id: <6lpp8r$ma4$5@csnews.cs.colorado.edu>
[courtesy cc of this posting sent to cited author via email]
In comp.lang.perl.misc,
Dave Hutchins <djhutchx@co.intel.com> writes:
:I can not find any reason why simple operations in perl return
:inaccurate results,
:such as (12 - 11.96) != 0.04
May Kronecker have mercy on your soul for comparing floats.
They aren't integer, which God created. They are a cheap
but useful immitation, resembling Platonic number only in the way that
your lifespan resembles infinity.
+------------------------------------------------+
| +--------------------------------------------+ |
| | +----------------------------------------+ | |
| | | Thou Shalt Not Compare Floats Directly | | |
| | +----------------------------------------+ | |
| +--------------------------------------------+ |
+------------------------------------------------+
I know this is in the FAQ. It's even in newer versions of
perldata.
:bc and awk return the correct results:
bc is a special case.
:toybox% bc
:scale=20
:(12 - 11.96)
:.04
:qu
:toybox% awk 'BEGIN{ print (12 - 11.96);exit}'
:0.04
You are being mislead. Let's try that one again:
% awk 'BEGIN{ print (0.04 == (12 - 11.96));exit}'
0
Well, lookee here! They don't seem the same after all,
now do they?
:toybox:
:
:but perl does not
:toybox% perl -e 'print (12 - 11.96); print "\n"; exit'
:0.0399999999999991
% perl -e 'printf "%.20f\n", (12 - 11.96)'
0.03999999999999914735
$ awk 'BEGIN{ printf "%.20f\n", (12 - 11.96);exit}'
0.03999999999999914735
Same answer. Same issue.
:does anyone have a simple answer?
God created the integers. Those are not integers.
They ought not be compared.
For more, vide faqwards.
--tom
--
It is, of course, written in Perl. Translation to C is left as an
exercise for the reader. :-) --Larry Wall in <7448@jpl-devvax.JPL.NASA.GOV>
------------------------------
Date: 11 Jun 1998 21:35:44 GMT
From: pburch@bcm.tmc.edu (Paula Burch)
Subject: perl training?
Message-Id: <6lpijg$jig@gazette.bcm.tmc.edu>
My boss wants me to take a perl class. My other duties distract me
too much of the time for me to have learned as much on my own as I'd
like. Can anyone recommend a perl training class in the Houston area?
Info from those in the business of teaching would be welome.
(I've restricted propagation of this message to within Houston, Texas:
my apologies if your newsreader picks it up outside the area anyway.)
--
Paula Burch
pburch@bcm.tmc.edu
http://mbcr.bcm.tmc.edu/pburch.html or http://www.flash.net/~pburch/
------------------------------
Date: Thu, 11 Jun 1998 23:44:26 GMT
From: Eric Bohlman <ebohlman@netcom.com>
Subject: Re: Please Help !!!
Message-Id: <ebohlmanEuEvA3.1u0@netcom.com>
Curtis Howard <howardcs@thnet.com> wrote:
: I'm trying to write a script that allows for a generic version of an
: online ordering system. Everything works fine except for my Check_Form
: Routine. I would like to require certain fields so that orders are
: not sent without contact information. Can someone please take a look at
: my script and let me know what I am doing wrong, or just point me in the
: right direction ? Any help would be greatly appreciated and I would be
: happy to mention your name in the script documentation. Thank You.
Normally, posting a large script and asking for review isn't going to get
you any responses. As it turns out, I chose to glance at your script and
something jumped out at me right away, so I'll have a go. However,
you'll also have to put up with me pointing out a number of other
problems, and style issues, that need work; keep in mind that I'm not
going to put in the time to deal with all of them, so don't assume you'll
have fixed everything if you only address the issues I bring up.
: #!/usr/bin/perl
You really should be using a -w switch on this line, at least until the
script is fully debugged.
: sub Check_Form {
: foreach $item (@REQUIRE) {
: if (!defined @FORM{'$item'}) {
You almost certainly want to write "$FORM" here. Your syntax is calling
for a hash slice, not an individual item.
: $error = 1;
: }
: }
: }
: sub Load_Prefs {
: $REQUIRE = {'firstname', 'lastname', 'phonenumber', 'email'};
This sets $REQUIRE to a reference to an anonymous hash with two key/value
pairs. The value of the 'firstname' key is 'lastname' and the value of
the 'phonenumber' key is 'email'. This can't possibly be what you want
to do.
BTW, it's considered bad form to use all-uppercase names for anything
other than filehandles and simple constants.
: $Config{'recipient'} = 'info@bernardcchocolate.com';
: $Cost{'CCB13'} = 12.00; $Cost{'GWB13'} = 14.00;
: $Cost{'CCB12'} = 18.00; $Cost{'GWB12'} = 20.00;
: $Cost{'CCB1'} = 36.00; $Cost{'GWB1'} = 38.00;
There are *much* easier and less error-prone ways to initialize a hash.
I suggest a look at the perldata manpage.
: sub Get_Order_Num {
: open(COUNTER, "< ordernum.txt") || die "Busy";
: $OrderNum = <COUNTER>;
: close(COUNTER);
: #increment count and write to file
: $OrderNum++;
: open(COUNTER, "> ordernum.txt") || "Busy";
: print COUNTER $OrderNum;
: close (COUNTER);
: }
This is guaranteed to generate duplicated or skipped order numbers,
because multiple instances of your script can be running at once. Read
up on concurrency control, particularly file locking.
: sub Parse_Form {
: read(STDIN, $input, $ENV{'CONTENT_LENGTH'});
: @pairs = split(/&/, $input);
You should really be using the CGI.pm module here, rather than trying to
handle this yourself. This piece of cut-and-pasted code is well-known to
fail in certain circumstances. You've also needlessly restricted
yourself to using the POST method of form submission.
: sub Create_HTML {
: print "Content-type: text/html\n\n";
: print "<HTML>\n<HEAD>\n";
: print "<TITLE>Order Number: $OrderNum</TITLE>\n";
: print "</HEAD>\n";
: print "<BODY BGCOLOR=\"#ffffff\">\n";
Read up on "here documents." Using one here would have made your code
much shorter and clearer, and cured the rather severe case of Leaning
Toothpick Syndrome.
: if ($FORM{CCB12} != 0) {
: print "<TR>\n<TD ALIGN = CENTER VALIGN = BOTTOM>Copper Chest Box (1/2 lb.)</TD>\n";
: print "<TD ALIGN = CENTER VALIGN = BOTTOM>$FORM{CCB12}</TD>\n";
: print "<TD ALIGN = CENTER VALIGN = BOTTOM>\$ $ItemTotal{CCB12}<TD>\n</TR>\n"; }
: if ($FORM{CCB1} != 0) {
: print "<TR>\n<TD ALIGN = CENTER VALIGN = BOTTOM>Copper Chest Box (1 lb.)</TD>\n";
: print "<TD ALIGN = CENTER VALIGN = BOTTOM>$FORM{CCB1}</TD>\n";
: print "<TD ALIGN = CENTER VALIGN = BOTTOM>\$ $ItemTotal{CCB1}<TD>\n</TR>\n"; }
This chain of conditionals cries out for a loop and an appropriate data
structure.
: sub Send_Mail {
: open(MAIL, "|$Mail_Location -t");
: print MAIL "To: $Config{recipient} \n";
: print MAIL "From: $FORM{email}\n";
Later on you've got the same explicit chain of conditionals, but you also
fail to do any checking to make sure the mail actually got sent.
------------------------------
Date: 11 Jun 1998 21:26:49 GMT
From: sb@engelschall.com (Steffen Beyer)
Subject: Re: Prob in FAQ: Week of the year
Message-Id: <6lpi2p$bkv$1@en1.engelschall.com>
greene@gucc.org wrote:
> is there an 'official' rule for determining week 1 of a year? When does week
> 53 end, and week 1 begin? Is there an ISO standard for this?
Yes there is.
See http://www.engelschall.com/u/sb/download/Date-Calc/DIN1355/.
Yours,
--
Steffen Beyer <sb@engelschall.com>
Free Perl and C Software for Download: www.engelschall.com/u/sb/download/
"Perl is like sex: If you never had it, you wonder what the fuss is all
about. Once you had it, you never want to be without it again." (unknown)
------------------------------
Date: 11 Jun 1998 23:41:09 GMT
From: Tom Christiansen <tchrist@mox.perl.com>
Subject: Re: Prob in FAQ: Week of the year
Message-Id: <6lppul$ma4$8@csnews.cs.colorado.edu>
[courtesy cc of this posting sent to cited author via email]
In comp.lang.perl.misc,
sb@engelschall.com (Steffen Beyer) writes:
:See http://www.engelschall.com/u/sb/download/Date-Calc/DIN1355/.
Keep in mind that last time I checked, American work weeks did not
follow that. Perhaps this has changed. I got out of the work business
long ago. :-)
--tom
--
I already have too much problem with people thinking the efficiency of
a perl construct is related to its length. On the other hand, I'm
perfectly capable of changing my mind next week... :-) --lwall
------------------------------
Date: 11 Jun 1998 23:09:52 GMT
From: Tom Christiansen <tchrist@mox.perl.com>
Subject: Re: Stages in a pipeline
Message-Id: <6lpo40$ma4$3@csnews.cs.colorado.edu>
[courtesy cc of this posting sent to cited author via email]
In comp.lang.perl.misc, Scott Bronson <sbronson@opentv.com> writes:
:> (ftroop) return if $pid = open(STDOUT, "|-");
:You're a naughty, naughty, naughty and very clever boy Tom... (to
:paraphrase Bloom County}
You're just now figuring this out? :-) Although frankly, I'm more
accustomed to the clever in triplicate and the naughty in singlicate.
:Unfortunately, the pipe between each stage means that I have to print
:and then re-parse to move data between each stage. Doable, but I think
:that's making the computer work harder than it should.
Oh well. That's what it's there for. :-) Anyway, people write
makefiles and multistage pipelines all the time.
--tom
--
"If ease of use is the highest goal, we should all be driving golf carts."
--Larry Wall
------------------------------
Date: Thu, 11 Jun 1998 22:14:21 GMT
From: bkhilton@netcom.com (Brand and Karina Hilton)
Subject: Starting a Dallas Perl Mongers group
Message-Id: <bkhiltonEuEr3x.1DF@netcom.com>
Hello, all...
I'm trying to gauge the interest in a Perl Mongers group for
Dallas. If you live and/or work in the Dallas area and are
interested in periodically getting together with other Perl
afficionados, please drop me a line.
For more info on Perl Mongers groups, visit
http://www.pm.org
Brand
------------------------------
Date: 11 Jun 1998 16:47:33 -0700
From: eric@sonic.net (Eric Eisenhart)
Subject: Re: Vote today, read CFV for c.l.p.moderated, Post the CFV here today,
Message-Id: <6lpqal$eqs@bolt.sonic.net>
In article <6lopk3$9ae$1@csnews.cs.colorado.edu>,
Tom Christiansen <tchrist@mox.perl.com> wrote:
> [courtesy cc of this posting sent to cited author via email]
>
>In comp.lang.perl.misc, pudge@pobox.com (Chris Nandor) writes:
>:It is against the rules to repost the CFV, and the CFV was
>:already posted here anyway.
>
>True on both counts. Unfortunately, those of us who kill crossposts
>consequently missed it (like me).
Send email to mcq@best.com (the votetaker) requesting a copy of the CFV for
comp.lang.perl.moderated.
(I missed it, too, but my crosspost killer shouldn't have killed something
with so few newsgroups...)
--
Eric Eisenhart -- http://www.eric.eisenhart.com
Help, I've gotten stuck in this .sig and I don't know how to get out!
------------------------------
Date: 8 Mar 97 21:33:47 GMT (Last modified)
From: Perl-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 8 Mar 97)
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.misc (and this Digest), send your
article to perl-users@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.
The Meta-FAQ, an article containing information about the FAQ, is
available by requesting "send perl-users meta-faq". The real FAQ, as it
appeared last in the newsgroup, can be retrieved with the request "send
perl-users FAQ". Due to their sizes, neither the Meta-FAQ nor the FAQ
are included in the digest.
The "mini-FAQ", which is an updated version of the Meta-FAQ, is
available by requesting "send perl-users mini-faq". It appears twice
weekly in the group, but is not distributed in the digest.
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 V8 Issue 2849
**************************************
