[25065] in Perl-Users-Digest
Perl-Users Digest, Issue: 7315 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Oct 27 00:06:02 2004
Date: Tue, 26 Oct 2004 21:05: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 Tue, 26 Oct 2004 Volume: 10 Number: 7315
Today's topics:
Re: Automatic way to get a list of Perl functions? <someone@example.com>
Re: Common file operations (Seymour J.)
Re: Common file operations (Seymour J.)
Re: Common file operations (Seymour J.)
Re: Common file operations <usa1@llenroc.ude.invalid>
Re: Compiling or Hiding Perl <1usa@llenroc.ude.invalid>
Re: Compiling or Hiding Perl <william@wilbur.25thandClement.com>
Re: Compiling or Hiding Perl <sbryce@scottbryce.com>
Re: Compiling or Hiding Perl <mjcarman@mchsi.com>
FAQ 8.7: How do I clear the screen? <comdog@panix.com>
Get Win32 Total Physical Memory & Available Physical Me <mirak63@carolina.rr.com>
Re: Get Win32 Total Physical Memory & Available Physica <usa1@llenroc.ude.invalid>
Re: how to fix code running old perl version? <mritty@gmail.com>
Re: how to fix code running old perl version? <abigail@abigail.nl>
Re: Linux vs. Windows: different behaviour [re rand()] <1usa@llenroc.ude.invalid>
Re: MAIL recommendation <noreply@gunnar.cc>
Re: MAIL recommendation <cwilbur@mithril.chromatico.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 26 Oct 2004 23:09:44 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Automatic way to get a list of Perl functions?
Message-Id: <YOAfd.8461$df2.4535@edtnps89>
El Duce wrote:
> Is there a way to automatically generate a list of valid Perl functions?
> I know how to query for modules, but short of fetching and trying to
> parse the output of "perldoc perlfunc," does anyone know a way?
$ perldoc perlfunc 2> /dev/null | perl -lne'
@func{ grep [ s!/.+!! ], m!"([a-zA-Z/]+)"!g } = ()
if /Perl Functions by Category/ .. /Alphabetical Listing of Perl Functions/
} { print for sort keys %func '
John
--
use Perl;
program
fulfillment
------------------------------
Date: Tue, 26 Oct 2004 19:51:46 -0300
From: "Shmuel (Seymour J.) Metz" <spamtrap@library.lspace.org.invalid>
Subject: Re: Common file operations
Message-Id: <417ee312$4$fuzhry+tra$mr2ice@news.patriot.net>
In <251020041625004613%jgibson@mail.arc.nasa.gov>, on 10/25/2004
at 04:25 PM, Jim Gibson <jgibson@mail.arc.nasa.gov> said:
>What computer language allows you to enter a partial file name and
>get a complete path?
REXX.
>Or do you mean you have a partial or relative path
>representation and you want to get the full, absolute path name?
Yes.
>If the latter, check out the File::Spec::Unix module or its brethren.
File::Spec::canonpath doesn't do it.
>[answered elsewhere in this thread]
Not really. What was elsewhere in the thread was that I could write
code to do it, using File::Find, which I had said I'd like to avoid. I
was looking for an equivalent to
if file = '' then file = 'forward+*'
CALL SysFileTree file, files, FOS
which returns an array of file names, including drive and directory
information.
[1] Well, close enough.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>
Unsolicited bulk E-mail subject to legal action. I reserve the
right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to spamtrap@library.lspace.org
------------------------------
Date: Tue, 26 Oct 2004 19:37:05 -0300
From: "Shmuel (Seymour J.) Metz" <spamtrap@library.lspace.org.invalid>
Subject: Re: Common file operations
Message-Id: <417edfa1$3$fuzhry+tra$mr2ice@news.patriot.net>
In <ywffd.5216$LT1.3686@trnddc09>, on 10/25/2004
at 10:56 PM, "J rgen Exner" <jurgenex@hotmail.com> said:
>Your question is not clear to me. Or maybe it is actually two
>questions?
First, some background. In OS/2 there is no[1] concept of mounting a
directory; instead, file systems are referred to by drive letter,
there is a current dirve and each drive letter has an associated CWD.
A file specification of the form[2] d:\name.ext is interpreted as
d:\cwd\name.ext, a name of the form name.ext is interpreted as being
in the cwd of the current drive and a name of the form \path\name.ext
is interpreted as being in the specified directory on the current
drive. I'd like to allow the user to specify any of the forms and
convert them to d:\path\name.ext.
>First part would be to get the list of all filename, which match the
>given partial name. Please note, typically this is not a 1:1
>relationship but a 1:n because a given partial name can be
>completed into many actual names.
Of course.
>And the second part would be how to prepend the CWD to the file
>names found. That's a trivial job for the double quote operator or
>the concatenation operator ".".
Simple but not trivial, because I have to first test whether the drive
is already their and whether the absolute path is already there.
>Where did you find a function "canon"?
Sorry, that's a typo. It's the canonpath method of the File:Spec
module. It's in the online Perl documentation and also in the
Dromedary.
>Where did you find a function "canon"? glob() is the right tool.
No, glob() expands wildcards but does not fill in implied components.
>Please show us the actual code,
extproc G:\emx\bin\perl -STw
#!/usr/bin/perl -Tw
#
use constant TRUE => 1;
use constant FALSE => '';
use File::Spec qw(catdir catfile splitdir splitpath);
#ARGV=('m*','xyz');
my ($dir,$file)=@ARGV;
print '@ARGV=(',join(',',@ARGV),")\n";
print '$dir =',"$dir\n";
$dir =~ s/^\'?([^\']*)\'?$/$1/;
print '$dir =',"$dir\n";
print '$file=',"$file\n";
$file =~ s/^\'?([^\']*)\'?$/$1/;
print '$file=',"$file\n";
my @dirs=glob($dir);
print '@dirs=(',join(',',@dirs),")\n";
unless (scalar(@dirs) == 1) {
print "$dir matches multiple directory names:\n";
die ' ', join("\n ",@dirs),"\n"
}
die "$dir is an invalid directory name.\n" unless -d $dir;
>What is a file specification in your terminlogoy?
I'd probably want to support the OS/2 conventions, which use * and ?
as wildcards, with ? matching a single component. I haven't decided
whether to restrict the input a bit or to translate into a regular
expression. d:\m?file.* would match, e.g., d:\cwd\mafile.cmd,
d:\cwd\mbfile.exe, d:\cwd\mcfile.html.
>If you want to recurse then use File::Find (and maybe stat() and
>other file information utilities to determine if each file matches
>the specification).
That's what I wanted to avoid :-(
Thanks.
[1] Well, yes, but that doesn't count. And it leaves the same
underlying problem.
[2] OS/2 uses \ as a separator rather than /.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>
Unsolicited bulk E-mail subject to legal action. I reserve the
right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to spamtrap@library.lspace.org
------------------------------
Date: Tue, 26 Oct 2004 19:36:00 -0300
From: "Shmuel (Seymour J.) Metz" <spamtrap@library.lspace.org.invalid>
Subject: Re: Common file operations
Message-Id: <417edf60$2$fuzhry+tra$mr2ice@news.patriot.net>
In <l30rn0d384u5798ibmbsl0raqf0g1qtrek@4ax.com>, on 10/26/2004
at 12:42 AM, Michele Dondi <bik.mido@tiscalinet.it> said:
>I don't trust you! (Minimal) examples?
If you don't trust me, then what's the point of giving you examples?
>Also, see 'perldoc -q glob'.
"No documentation found"
>Then just use File::Find.
I will if what I wanted doesn't exist.
>Ever heard about regexen?
No.
>Then glob() should do.
No.
>Again, you should show some actual example proving that it doesn't.
I might, for someone who isn't prejudiced. Why should I bother for
someone who already has made up her mind?
> perldoc -f glob
No documentation found for "perlfunc"
> perldoc File::Glob
I don't see anything there that wan't already in my de3ad tree.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>
Unsolicited bulk E-mail subject to legal action. I reserve the
right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to spamtrap@library.lspace.org
------------------------------
Date: 27 Oct 2004 04:00:37 GMT
From: "A. Sinan Unur" <usa1@llenroc.ude.invalid>
Subject: Re: Common file operations
Message-Id: <Xns958F1A83B87asu1cornelledu@132.236.56.8>
"Shmuel (Seymour J.) Metz" <spamtrap@library.lspace.org.invalid> wrote in
news:417edf60$2$fuzhry+tra$mr2ice@news.patriot.net:
> In <l30rn0d384u5798ibmbsl0raqf0g1qtrek@4ax.com>, on 10/26/2004
> at 12:42 AM, Michele Dondi <bik.mido@tiscalinet.it> said:
>
>>I don't trust you! (Minimal) examples?
>
> If you don't trust me, then what's the point of giving you examples?
He does not trust the assertions you make without providing test cases that
exhibit the problems you mention.
>>Also, see 'perldoc -q glob'.
>
> "No documentation found"
As it turns out, he was right not to trust you:
Found in C:\Perl\lib\pod\perlfaq5.pod
Is there a leak/bug in glob()?
Due to the current implementation on some operating systems, when you
use the glob() function or its angle-bracket alias in a scalar context,
you may cause a memory leak and/or unpredictable behavior. It's best
therefore to use glob() only in list context.
Why doesn't glob("*.*") get all the files?
Because even on non-Unix ports, Perl's glob function follows standard
Unix globbing semantics. You'll need "glob("*")" to get all (non-
hidden)
files. This makes glob() portable even to legacy systems. Your port may
include proprietary globbing functions as well. Check its documentation
for details.
You can also consult perldoc -f glob and perldoc perlop.
>>Then just use File::Find.
>
> I will if what I wanted doesn't exist.
You haven't described what you want.
>>Ever heard about regexen?
>
> No.
Then you shoud read
perldoc perlre
perldoc perlretut
etc so on and so forth.
>>Again, you should show some actual example proving that it doesn't.
>
> I might, for someone who isn't prejudiced.
Feel free to insist on not asking questions _the_ smart way. I think all of
us are prejudiced against people who describe their problems in inexact
verbal form rather than in Perl (by the way, have you read the posting
guidelines for this group. They are posted here regularly).
> Why should I bother for someone who already has made up her mind?
Are you related to Arnold Schwarzenegger by any chance? I would read the
name of the person I am corresponding with a little more carefully if I
were you.
>> perldoc -f glob
>
> No documentation found for "perlfunc"
Then you must have messed up your installation. Fix it soon. Programming
without documentation is not a good idea.
>> perldoc File::Glob
>
> I don't see anything there that wan't already in my de3ad tree.
???
Sinan
------------------------------
Date: 26 Oct 2004 22:13:46 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Compiling or Hiding Perl
Message-Id: <Xns958EB970E95C2asu1cornelledu@132.236.56.8>
"daniel kaplan" <nospam@nospam.com> wrote in
news:1098828143.236139@nntp.acecape.com:
>> First off, don't top -post.
>
> not sure this was aimed at me, don't think so, but hey precidents have
> been set
It is very easy to tell to whom I am referring because I do not, unlike
you, snip attributions. So, I am asking you not to snip attributions.
It is not quoting and commenting on the rest of the message because it will
take too long of my time to re-insert the correct attributions you snipped.
> but since you seem quite up-to-date, i will re-ask "you" directly if
> that's ok....do you know of any "organized effort" to try and make
> this a reality?
Read the FAQ on this topic.
Sinan.
------------------------------
Date: Tue, 26 Oct 2004 15:16:42 -0700
From: William Ahern <william@wilbur.25thandClement.com>
Subject: Re: Compiling or Hiding Perl
Message-Id: <avu252-cbf.ln1@wilbur.25thandClement.com>
daniel kaplan <nospam@nospam.com> wrote:
> which by the way is one problem with patenting something. you just look at
> the patent and devise a different way to do it. i am sure we will all be
> dead and buried before they figure out the right way to protect works like
> this..
The more pressing dilemma is how to protect us from the boogey man. In the
mean time, you keeping sarching for the man who failed to become a
millionaire because some people illegally redistributed his software.
You bought your lotto ticket today, right? Any day now, dude... any day....
(Yes, I'm being an ass, but I can't help it today. Don't take it
personally.)
------------------------------
Date: Tue, 26 Oct 2004 16:49:28 -0600
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: Compiling or Hiding Perl
Message-Id: <10ntl3kshpe3e84@corp.supernews.com>
William Ahern wrote:
> In the
> mean time, you keeping sarching for the man who failed to become a
> millionaire because some people illegally redistributed his software.
As opposed to a certain resident of Redmond, Washington who made his
millions BECAUSE people pirated his software.
------------------------------
Date: Tue, 26 Oct 2004 20:10:03 -0500
From: Michael Carman <mjcarman@mchsi.com>
Subject: Re: Compiling or Hiding Perl
Message-Id: <clmshf$93v1@onews.rockwellcollins.com>
daniel kaplan wrote:
>
> do you know of any "organized effort" to try and make this a reality?
If you search the archives of this group you'll uncover many threads
discussing this, including a few posts from people who thought that they
had "solved" this problem. There's also at least one commercial product.
That said, the general consensus of this group (which includes quite a
few people with *lots* of knowledge about Perl) is that any attempts to
do this are a wasted effort. The FAQ goes into more detail, but the
bottom line is that most methods of hiding your source code are
trivially defeated by any clueful Perl programmer.
I suggest saving your tuits for a less futile endeavor.
-mjc
------------------------------
Date: Wed, 27 Oct 2004 04:03:01 +0000 (UTC)
From: PerlFAQ Server <comdog@panix.com>
Subject: FAQ 8.7: How do I clear the screen?
Message-Id: <cln6ll$4tp$1@reader1.panix.com>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.
--------------------------------------------------------------------
8.7: How do I clear the screen?
If you only have do so infrequently, use "system":
system("clear");
If you have to do this a lot, save the clear string so you can print it
100 times without calling a program 100 times:
$clear_string = `clear`;
print $clear_string;
If you're planning on doing other screen manipulations, like cursor
positions, etc, you might wish to use Term::Cap module:
use Term::Cap;
$terminal = Term::Cap->Tgetent( {OSPEED => 9600} );
$clear_string = $terminal->Tputs('cl');
--------------------------------------------------------------------
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-2002 Tom Christiansen and Nathan
Torkington, and other contributors as noted. All rights
reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
------------------------------
Date: Tue, 26 Oct 2004 21:48:41 -0400
From: "Karim Wall" <mirak63@carolina.rr.com>
Subject: Get Win32 Total Physical Memory & Available Physical Memory stats
Message-Id: <UNqdncAz8fvrY-PcRVn-sA@giganews.com>
Hello. I've checked CPAN and have searched the net as well and have not been
able to find a Perl script or module that will get me the Total Physical
Memory and Available Physical Memory stats for a remote system, much less an
NT utility. The one utility I found, SYSTEMINFO.EXE can't be used to get
info on an NT4 system and I have plenty of them. I've found some scripts
that provide task mgr types of info but that's too much.
Any ideas?
Thanks,
Karim
------------------------------
Date: 27 Oct 2004 01:56:06 GMT
From: "A. Sinan Unur" <usa1@llenroc.ude.invalid>
Subject: Re: Get Win32 Total Physical Memory & Available Physical Memory stats
Message-Id: <Xns958EDF22EDC6Basu1cornelledu@132.236.56.8>
"Karim Wall" <mirak63@carolina.rr.com> wrote in
news:UNqdncAz8fvrY-PcRVn-sA@giganews.com:
> Hello. I've checked CPAN and have searched the net as well and have
> not been able to find a Perl script or module that will get me the
> Total Physical Memory and Available Physical Memory stats for a remote
> system, much less an NT utility.
Don't know about pulling information from remote machines but does:
http://tinyurl.com/5rl7e
help?
Sinan.
------------------------------
Date: Tue, 26 Oct 2004 18:09:00 -0400
From: Paul Lalli <mritty@gmail.com>
Subject: Re: how to fix code running old perl version?
Message-Id: <clmhtv$h9e$1@misc-cct.server.rpi.edu>
Abigail wrote:
> Paul Lalli (mritty@gmail.com) wrote on MMMMLXXIV September MCMXCIII in
> <URL:news:QNxfd.3372$Xq3.2564@trndny01>:
> {} Following the general rule that software is *never* completed, removing
> {} use strict enables him to do Bad Things when the software is inevitably
> {} updated.
>
> But surely, the software doesn't disappear from the 5.6 and 5.8 boxes
> it's running on, nor does the author degrade the perl he's developing
> on? There of course, 'use strict' remains were it is.
>
> But for the 5.005 ports, he removes the use strict.
Assuming the box with 5.005 will only be a production box, and that no
development work will ever happen to the script on that box, then yes I
agree.
I didn't necessarily get the impression that's true from the OP.
Paul Lalli
------------------------------
Date: 26 Oct 2004 22:56:50 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: how to fix code running old perl version?
Message-Id: <slrncntlhd.3ac.abigail@alexandra.abigail.nl>
Paul Lalli (mritty@gmail.com) wrote on MMMMLXXIV September MCMXCIII in
<URL:news:clmhtv$h9e$1@misc-cct.server.rpi.edu>:
() Abigail wrote:
() > Paul Lalli (mritty@gmail.com) wrote on MMMMLXXIV September MCMXCIII in
() > <URL:news:QNxfd.3372$Xq3.2564@trndny01>:
() > {} Following the general rule that software is *never* completed, removing
() > {} use strict enables him to do Bad Things when the software is inevitably
() > {} updated.
() >
() > But surely, the software doesn't disappear from the 5.6 and 5.8 boxes
() > it's running on, nor does the author degrade the perl he's developing
() > on? There of course, 'use strict' remains were it is.
() >
() > But for the 5.005 ports, he removes the use strict.
()
() Assuming the box with 5.005 will only be a production box, and that no
() development work will ever happen to the script on that box, then yes I
() agree.
()
() I didn't necessarily get the impression that's true from the OP.
The OP wrote:
I have a server that I'm not able to upgrade at the moment
that is running perl 5.005. My other servers are running
either perl 5.6 or perl 5.8. I have some code that is
distributed to all servers that will not run on perl 5.0005
and gives the error:
That doesn't give me any indication there are any plans to do development
work on the box that runs perl 5.005.
Abigail
--
# Perl 5.6.0 broke this.
%0=map{reverse+chop,$_}ABC,ACB,BAC,BCA,CAB,CBA;$_=shift().AC;1while+s/(\d+)((.)
(.))/($0=$1-1)?"$0$3$0{$2}1$2$0$0{$2}$4":"$3 => $4\n"/xeg;print#Towers of Hanoi
------------------------------
Date: 26 Oct 2004 22:34:12 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Linux vs. Windows: different behaviour [re rand()]
Message-Id: <Xns958EBCE81E40Fasu1cornelledu@132.236.56.8>
Michele Dondi <bik.mido@tiscalinet.it> wrote in
news:4d2tn0dt15g18n5s4nlat21dbfimcfg7ba@4ax.com:
> This spreaded from some tests I made in connection with the thread
> "Fast random string generation":
>
> # perl -le '$,="\t"; print unpack "C*", pack "L", rand 2**32 for
> 1..15'
I am not sufficiently at ease with pack to see if something is wrong
above.
> Does the cmt at the end of 'perldoc -f rand' apply? Note: 5.8.4 in
> both cases (AS under Windows).
Same version here. You got me curious. I have:
C:\Home> perl -MConfig -e"print qq{$Config{randbits}}
15
I also checked stdlib.h for the free command line compiler they have:
C:\Home> cl
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for
80x86
and it says
#define RAND_MAX 0x7fff
So those are consistent.
Then, I did:
use strict;
use warnings;
my @data;
push @data, rand for 1 .. 10_000;
open my $data, '>', 'data.txt' or die "data.txt: $!";
for (@data) { print $data "$_\n" }
__END__
Five times, and looked at the resulting emprical CDF in each case, they
were all straight lines from (0,0) to (100,100) so the output rand
generates is fairly uniformly distributed.
Dunno what you are observing but I don't think the bit about
If your rand function consistently returns numbers that
are too large or too small,
applies here.
Hope this helps.
Sinan.
------------------------------
Date: Wed, 27 Oct 2004 01:29:02 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: MAIL recommendation
Message-Id: <2u8540F26kircU1@uni-berlin.de>
Laura wrote:
> > Gunnar Hjalmarsson wrote:
>>>I mentioned Mail::Sender and MIME::Lite.
>
> Try Mail::Mailer.
It does not handle attachments, does it?
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Wed, 27 Oct 2004 02:32:33 GMT
From: Charlton Wilbur <cwilbur@mithril.chromatico.net>
Subject: Re: MAIL recommendation
Message-Id: <87pt34hpmp.fsf@mithril.chromatico.net>
>>>>> "lazy fuckwit" == daniel kaplan <nospam@nospam.com> writes:
lazy fuckwit> but in spouting FAQ, FAQ, FAQ...i'm sorry guys/gals,
lazy fuckwit> and i sincerely don't mean this with the venom a few
lazy fuckwit> of you have thrown at me, this is more like
lazy fuckwit> goose-stepping to me.
That's because the clueful people -- and you WANT clueful people
answering your questions -- are aware that their time is a limited
resource. Rather than typing a 1000-word response every time someone
like you can't be bothered to read the FAQ, they point people at the
FAQ. The idea of the posting guidelines (which I suspect you still
have not read) is that there are things that routinely annoy the
clueful people, and the clueful people know this; so in the interests
of providing help to the most people, they alert people as to what
annoys them and wastes their time.
What you are doing is the equivalent of shoving your way to the front
of the line and demanding the attention of all the clerks at once,
then shouting at them for their rudeness when they point out that
queues exist for a reason.
lazy fuckwit> may i suggest you do the same, see
lazy fuckwit> what some of the other programming groups do?
lazy fuckwit> you'll find stupid "dooooh" posts from EVERYONE.
lazy fuckwit> but you'll find so few of them illicit terse
lazy fuckwit> responses. that keeps everyone coming coming back
lazy fuckwit> for more, knowing that an answer is always just a
lazy fuckwit> few clicks away, that keeps more software flowing,
lazy fuckwit> and so on and so on and so on.
I think of this group and comp.lang.c as two of the most useful groups
I have ever participated in. If you think the treatment you have
received here is rough, go ask an off-topic question in comp.lang.c.
Further, this group is extremely valuable *technically* -- if I have a
serious Perl question, I can ask it here, and there *will* be experts
who can help. I have a vested interest in not driving them off with
what you refer to as "dooooh" posts. If this group turns into a
social group for newbies to help each other learning Perl -- which is
what you seem to think it should be -- then it will be useless for
difficult technical questions. And as there are many other fora for
newbies to help each other learning Perl, and precious few fora where
Perl wizards may be consulted, this forum's value as the latter is
dependent on not driving the wizards off. And thus, the Posting
Guidelines and habits of etiquette that you so summarily dismiss
because that way you can't ask FAQs for the thousandth time.
Charlton
--
cwilbur at chromatico dot net
cwilbur at mac dot com
------------------------------
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 7315
***************************************
