[25100] in Perl-Users-Digest
Perl-Users Digest, Issue: 7350 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Nov 2 06:05:56 2004
Date: Tue, 2 Nov 2004 03:05:06 -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 Tue, 2 Nov 2004 Volume: 10 Number: 7350
Today's topics:
Re: Common file operations (Seymour J.)
Re: Common file operations (Seymour J.)
Re: Common file operations <uri@stemsystems.com>
Re: Common file operations <bik.mido@tiscalinet.it>
Extracting Directories and Sub Directories and Counting (Ron Smith)
Re: Extracting Directories and Sub Directories and Coun <bik.mido@tiscalinet.it>
FAQ 7.22: How do I create a switch or case statement? <comdog@panix.com>
FAQ 8.7: How do I clear the screen? <comdog@panix.com>
Global @INC <william@wilbur.25thandClement.com>
Re: Global @INC <usa1@llenroc.ude.invalid>
Re: Global @INC <ebohlman@omsdev.com>
how to find the fastest cpan mirror site? <x.t.hua@163.com>
Re: how to find the fastest cpan mirror site? (Anno Siegel)
number of characters in a string (machoq)
Re: number of characters in a string <abigail@abigail.nl>
Re: number of characters in a string <jgibson@mail.arc.nasa.gov>
Re: Perl is awsome! <bik.mido@tiscalinet.it>
Re: Perl is awsome! <vetro@online.no>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Regular Expression for - \C\R... <gis86508@cissol1.cis.nctu.edu.tw>
Re: Regular Expression for - \C\R... (Anno Siegel)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sun, 31 Oct 2004 00:44:08 -0300
From: "Shmuel (Seymour J.) Metz" <spamtrap@library.lspace.org.invalid>
Subject: Re: Common file operations
Message-Id: <41846d98$15$fuzhry+tra$mr2ice@news.patriot.net>
In <55s3o011qguibo2r9dh551f2afhs82okch@4ax.com>, on 10/29/2004
at 10:04 AM, Michele Dondi <bik.mido@tiscalinet.it> said:
>Yes, but also instead of the cmt explaining what should be in @ARGV.
Actually, that was code that was commented out.
>Indicating that "my" solution *may* be 80% faster than "yours".
Okay, I've changed the code to
my $dir=shift;
s/^'//, s/'$// for $dir;
print '$dir =',"$dir\n";
print '@ARGV=(',join(',',@ARGV),")\n";
my @files=@ARGV;
my @dirs=grep -d, glob abs_path($dir);
if $dirs==0 {
die "$dir dosn't match any directory names:\n";
}
elsif $dir>1 {
print "$dir matches multiple directory names:\n";
die join " \n" @dirs, "\n";
}
>Also, search 'WARNING' in perldoc perlre.
Are you referring to the issue of $1 versus \1?
>BTW: "Q&D"? (Sorry, I'm not a native English speaker.)
Quick and dirty, IOW, a hack.
> perldoc perlop
Thanks. It turned out to be easier to find it in the dead tree. The
code in question was strictly for debugging, and the messages are
terse because that's all I need for my purposes; I certainly won't put
them into production code. Is it considered good style to use a
here-doc when the output is only a line or two?
>However, wrt the code you posted, something like:
If I were adding snapshot code to a production routine then I'd
probably do something like that, but what I've posted so far was
intended to be thrown out once I had everything nailed down. I agree
that were I to add more verbose diagnostics then the here-doc would be
cleaner. And, in fact, I've used that elsewhere; I just didn't
remember the nomenclature.
--
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: Sun, 31 Oct 2004 00:48:56 -0300
From: "Shmuel (Seymour J.) Metz" <spamtrap@library.lspace.org.invalid>
Subject: Re: Common file operations
Message-Id: <41846eb8$16$fuzhry+tra$mr2ice@news.patriot.net>
In <Xns9590B57C97B18asu1cornelledu@132.236.56.8>, on 10/28/2004
at 09:50 PM, "A. Sinan Unur" <1usa@llenroc.ude.invalid> said:
>On the other hand, when you say partial, one thinks of a file
>specification such as te??.p* or even c:\dir\path\more\te??.p* Both
>of those patterns are partial file names.
That wasn't my intent.
>See File::Find::Rule
Thanks.
>Feel free to search CPAN next time.
The problem is knowing what to search for.
--
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, 02 Nov 2004 05:43:08 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Common file operations
Message-Id: <x7d5ywst5f.fsf@mail.sysarch.com>
>>>>> "SM" == Shmuel (Seymour J ) Metz <spamtrap@library.lspace.org.invalid> writes:
SM> my $dir=shift;
SM> s/^'//, s/'$// for $dir;
SM> print '$dir =',"$dir\n";
SM> print '@ARGV=(',join(',',@ARGV),")\n";
SM> my @files=@ARGV;
SM> my @dirs=grep -d, glob abs_path($dir);
SM> if $dirs==0 {
what is $dirs? did you even run this under strict? please post real code
and not some made up random text. maybe you meant it to be @dirs which
make sense but why post code that you never ran even to check for syntax
and strictness?
FYI @dirs and $dirs have no relationship
also use a little white space. it won't hurt you a bit and it's free!
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: Tue, 02 Nov 2004 10:57:22 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Common file operations
Message-Id: <70keo011k00rvdigeim4mculkp9aab2j1u@4ax.com>
On Sun, 31 Oct 2004 00:44:08 -0300, "Shmuel (Seymour J.) Metz"
<spamtrap@library.lspace.org.invalid> wrote:
>Okay, I've changed the code to
>
> my $dir=shift;
> s/^'//, s/'$// for $dir;
> print '$dir =',"$dir\n";
> print '@ARGV=(',join(',',@ARGV),")\n";
Not that I despise join(), but IMHO it would be more terse having it
take place under the curtain, a la (e.g.)
{
local $,=',';
print "@ARGV\n";
}
> my @files=@ARGV;
> my @dirs=grep -d, glob abs_path($dir);
> if $dirs==0 {
> die "$dir dosn't match any directory names:\n";
> }
Huh?!? Are you running Perl6? If not then this has to be:
if ($dirs==0) {
# ^ ^
die "$dir dosn't match any directory names:\n";
}
But then it's also @dirs, not $dirs.
> elsif $dir>1 {
Still running Perl6, I see... ;-)
Also... well, here $dir at least does exist. But @dirs is again what
you really want, isnt'it?
> print "$dir matches multiple directory names:\n";
> die join " \n" @dirs, "\n";
Is there any good reason you are mixing print() and die() statements?
Are you aware you will be printing to two different fd's?
Also, the last line has an error: join() wants comma separated args,
but in that case you must also add parenthesis to avoid the last "\n"
being considered as another argument to join().
Moreover, out of curiosity: why " \n" instead of "\n"?
All in all I'd rewrite the whole fragment as:
@dirs or die "`$dir' doesn't match any directory name\n";
die "`$dir' matches multiple directory names:\n",
map "$_\n", @dirs if @dirs>1;
>>Also, search 'WARNING' in perldoc perlre.
>
>Are you referring to the issue of $1 versus \1?
No, I suggested you to search 'WARNING' in perldoc perlre. This turns
out to be:
| WARNING: Once Perl sees that you need one of $&, $`, or $' anywhere in
| the program, it has to provide them for every pattern match. This may
| substantially slow your program. Perl uses the same mechanism to produce
| $1, $2, etc, so you also pay a price for each pattern that contains
| capturing parentheses. (To avoid this cost while retaining the grouping
| behaviour, use the extended regular expression "(?: ... )" instead.) But
| if you never use $&, $` or $', then patterns *without* capturing
| parentheses will not be penalized. So avoid $&, $', and $` if you can,
| but if you can't (and some algorithms really appreciate them), once
| you've used them once, use them at will, because you've already paid the
| price. As of 5.005, $& is not so costly as the other two.
>them into production code. Is it considered good style to use a
>here-doc when the output is only a line or two?
One or two lines... hmmm, I would say: no. Just a few more and then:
yes. In both cases this is largely a matter of personal tastes.
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: 1 Nov 2004 20:48:39 -0800
From: geeksatlarge@yahoo.com (Ron Smith)
Subject: Extracting Directories and Sub Directories and Counting
Message-Id: <d408246c.0411012048.cee264b@posting.google.com>
#!/usr/bin/perl
use strict;
print "\n";
my %HoA;
for ( `dir /b/s` ) {
push @{ $HoA{$1} }, $2 if /(.+)\\(\w+)\.\d+\.\w+$/;
}
for my $dir ( sort keys %HoA ) {
print join ( "\n", $dir ), "\n\n";
my @basenames = @{ $HoA{$dir} };
my %count;
for my $frames ( @basenames ) {
$count{$frames} += 1;
}
for ( sort keys %count ) {
printf "%30s\t%04d\n", $_, $count{$_};
}
print "\n";
}
gives me:
file_base_name file_count
in two columns. How would I add additional columns like:
file_base_name file_count File_extension file_size
Which construct would I use? Would it be a 'HoH', or simply expand on
a 'HoA', or is it another construct like 'AoA' or AoH?
Any help would be appreciated.
TIA
Ron
------------------------------
Date: Tue, 02 Nov 2004 10:57:24 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Extracting Directories and Sub Directories and Counting
Message-Id: <l5meo09a2381j53m5ut59elf2729io01ri@4ax.com>
On 1 Nov 2004 20:48:39 -0800, geeksatlarge@yahoo.com (Ron Smith)
wrote:
>#!/usr/bin/perl
[snip code]
Please don't take my words as a personal attack, but this made my
heart really hurt. I didn't even try to understand your code. What do
you really want to do? Maybe someone may suggest more effective ways
to do it.
Also, the 'dir /b/s' bit suggests you may be interested in File::Find,
anyway.
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: Tue, 2 Nov 2004 05:03:03 +0000 (UTC)
From: PerlFAQ Server <comdog@panix.com>
Subject: FAQ 7.22: How do I create a switch or case statement?
Message-Id: <cm74e6$aov$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.
--------------------------------------------------------------------
7.22: How do I create a switch or case statement?
This is explained in more depth in the perlsyn. Briefly, there's no
official case statement, because of the variety of tests possible in
Perl (numeric comparison, string comparison, glob comparison, regex
matching, overloaded comparisons, ...). Larry couldn't decide how best
to do this, so he left it out, even though it's been on the wish list
since perl1.
Starting from Perl 5.8 to get switch and case one can use the Switch
extension and say:
use Switch;
after which one has switch and case. It is not as fast as it could be
because it's not really part of the language (it's done using source
filters) but it is available, and it's very flexible.
But if one wants to use pure Perl, the general answer is to write a
construct like this:
for ($variable_to_test) {
if (/pat1/) { } # do something
elsif (/pat2/) { } # do something else
elsif (/pat3/) { } # do something else
else { } # default
}
Here's a simple example of a switch based on pattern matching, this time
lined up in a way to make it look more like a switch statement. We'll do
a multiway conditional based on the type of reference stored in
$whatchamacallit:
SWITCH: for (ref $whatchamacallit) {
/^$/ && die "not a reference";
/SCALAR/ && do {
print_scalar($$ref);
last SWITCH;
};
/ARRAY/ && do {
print_array(@$ref);
last SWITCH;
};
/HASH/ && do {
print_hash(%$ref);
last SWITCH;
};
/CODE/ && do {
warn "can't print function ref";
last SWITCH;
};
# DEFAULT
warn "User defined type skipped";
}
See "perlsyn/"Basic BLOCKs and Switch Statements"" for many other
examples in this style.
Sometimes you should change the positions of the constant and the
variable. For example, let's say you wanted to test which of many
answers you were given, but in a case-insensitive way that also allows
abbreviations. You can use the following technique if the strings all
start with different characters or if you want to arrange the matches so
that one takes precedence over another, as "SEND" has precedence over
"STOP" here:
chomp($answer = <>);
if ("SEND" =~ /^\Q$answer/i) { print "Action is send\n" }
elsif ("STOP" =~ /^\Q$answer/i) { print "Action is stop\n" }
elsif ("ABORT" =~ /^\Q$answer/i) { print "Action is abort\n" }
elsif ("LIST" =~ /^\Q$answer/i) { print "Action is list\n" }
elsif ("EDIT" =~ /^\Q$answer/i) { print "Action is edit\n" }
A totally different approach is to create a hash of function references.
my %commands = (
"happy" => \&joy,
"sad", => \&sullen,
"done" => sub { die "See ya!" },
"mad" => \&angry,
);
print "How are you? ";
chomp($string = <STDIN>);
if ($commands{$string}) {
$commands{$string}->();
} else {
print "No such command: $string\n";
}
--------------------------------------------------------------------
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, 2 Nov 2004 11:03:02 +0000 (UTC)
From: PerlFAQ Server <comdog@panix.com>
Subject: FAQ 8.7: How do I clear the screen?
Message-Id: <cm7ph6$fuo$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: Mon, 1 Nov 2004 18:28:08 -0800
From: William Ahern <william@wilbur.25thandClement.com>
Subject: Global @INC
Message-Id: <ou7j52-1b6.ln1@wilbur.25thandClement.com>
How can I globally specify additional @INC paths. Is there a module I can
edit amongst any Perl library modules--written in perl?
I've tried setting PERL5LIB in the the global shell startup files in /etc,
but that doesn't work for perl code started from init. Recompiling perl
isn't an option.
TIA,
Bill
------------------------------
Date: 2 Nov 2004 02:39:24 GMT
From: "A. Sinan Unur" <usa1@llenroc.ude.invalid>
Subject: Re: Global @INC
Message-Id: <Xns9594DC4CFB6D7asu1cornelledu@132.236.56.8>
William Ahern <william@wilbur.25thandClement.com> wrote in
news:ou7j52-1b6.ln1@wilbur.25thandClement.com:
> How can I globally specify additional @INC paths. Is there a module I
> can edit amongst any Perl library modules--written in perl?
>
> I've tried setting PERL5LIB in the the global shell startup files in
> /etc, but that doesn't work for perl code started from init.
> Recompiling perl isn't an option.
Hmmm ...
perl -h
...
-Idirectory specify @INC/#include directory (several -I's allowed)
...
Sinan
------------------------------
Date: 2 Nov 2004 04:17:44 GMT
From: Eric Bohlman <ebohlman@omsdev.com>
Subject: Re: Global @INC
Message-Id: <Xns9594E3CE5E814ebohlmanomsdevcom@130.133.1.4>
William Ahern <william@wilbur.25thandClement.com> wrote in
news:ou7j52-1b6.ln1@wilbur.25thandClement.com:
> How can I globally specify additional @INC paths. Is there a module I
> can edit amongst any Perl library modules--written in perl?
>
> I've tried setting PERL5LIB in the the global shell startup files in
> /etc, but that doesn't work for perl code started from init.
> Recompiling perl isn't an option.
'perldoc lib' brings up a description that starts out:
"This is a small simple module which simplifies the manipulation of @INC
at compile time.
"It is typically used to add extra directories to perl's search path so
that later "use" or "require" statements will find modules which are not
located on perl's default search path."
Sounds exactly like what you're looking for.
------------------------------
Date: Tue, 2 Nov 2004 10:04:15 +0000 (UTC)
From: XiaotingHua <x.t.hua@163.com>
Subject: how to find the fastest cpan mirror site?
Message-Id: <slrncofiuq.2fo.kenneth@xthua.localdomain>
i will mirror CPAN to our intranet.and i looked at the CPAN FAQ,and find how to mirror the CPAN site.i will try to use rsync.and the faq also give out the command and some sites.but i can't decide choose which one.
and then i use the perl of module Geo::IPfree to find the country which the site in. but that is useless ,for the distance is not equal to the speed.
would you like to give me some advises? thank you.
------------------------------
Date: 2 Nov 2004 10:33:21 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: how to find the fastest cpan mirror site?
Message-Id: <cm7nph$5df$2@mamenchi.zrz.TU-Berlin.DE>
XiaotingHua <x.t.hua@163.com> wrote in comp.lang.perl.misc:
> i will mirror CPAN to our intranet.and i looked at the CPAN FAQ,and find
> how to mirror the CPAN site.i will try to use rsync.and the faq also
> give out the command and some sites.but i can't decide choose which one.
>
> and then i use the perl of module Geo::IPfree to find the country which
> the site in. but that is useless ,for the distance is not equal to the
> speed.
>
> would you like to give me some advises? thank you.
What's the big worry? Start with a sensible choice based on geographical
closeness. If it works in reasonable time, stick with it. If it doesn't,
try another.
Anno
------------------------------
Date: 1 Nov 2004 15:51:42 -0800
From: spamsaket@yahoo.com (machoq)
Subject: number of characters in a string
Message-Id: <e715de76.0411011551.3fb201c7@posting.google.com>
I have reading a line from a text file
the line is like
abc\"123
I need to find the number of characters in this string... (which
should be 8, however if i do a
$var = $line;
print length($var); i get 7
How do i workaround it ?
regards
-Machoq !
------------------------------
Date: 02 Nov 2004 00:32:21 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: number of characters in a string
Message-Id: <slrncodlcl.43o.abigail@alexandra.abigail.nl>
machoq (spamsaket@yahoo.com) wrote on MMMMLXXX September MCMXCIII in
<URL:news:e715de76.0411011551.3fb201c7@posting.google.com>:
\\ I have reading a line from a text file
\\ the line is like
\\
\\ abc\"123
\\ I need to find the number of characters in this string... (which
\\ should be 8, however if i do a
\\
\\ $var = $line;
\\ print length($var); i get 7
\\
\\ How do i workaround it ?
Well, a workaround would be:
print 8;
Of course, if you want to know what you did wrong, you need
to tell us what you did. Since we don't know what's in $line,
and how it got there, we can't tell you anything useful.
Abigail
--
#!/opt/perl/bin/perl -- # No trailing newline after the last line!
BEGIN{$|=$SIG{__WARN__}=sub{$_=$_[0];y-_- -;print/(.)"$/;seek _,-open(_
,"+<$0"),2;truncate _,tell _;close _;exec$0}}//rekcaH_lreP_rehtona_tsuJ
------------------------------
Date: Mon, 01 Nov 2004 17:17:43 -0800
From: Jim Gibson <jgibson@mail.arc.nasa.gov>
Subject: Re: number of characters in a string
Message-Id: <011120041717431034%jgibson@mail.arc.nasa.gov>
In article <e715de76.0411011551.3fb201c7@posting.google.com>, machoq
<spamsaket@yahoo.com> wrote:
> I have reading a line from a text file
> the line is like
>
> abc\"123
> I need to find the number of characters in this string... (which
> should be 8, however if i do a
>
> $var = $line;
> print length($var); i get 7
>
> How do i workaround it ?
> regards
> -Machoq !
Works for me:
Jim 44% cat machoq.pl
#!/usr/local/bin/perl
#
use warnings;
use strict;
while(my $line = <DATA>) {
chomp($line);
print $line, " has ", length($line), " characters\n";
}
__DATA__
abc\"123
Jim 45% machoq.pl
abc\"123 has 8 characters
Jim 46%
------------------------------
Date: Tue, 02 Nov 2004 10:57:23 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Perl is awsome!
Message-Id: <uuleo09ihnhd08djd8k3lob2o3jaikf531@4ax.com>
On Mon, 01 Nov 2004 22:26:13 -0000, Bjarne Stroustrup
<bs@research.att.com> wrote:
>Scalars, arrays, hashes, references, modules...
>Perl is so cool! Why didn't I think of it?
>
>How about Perl++?
Perl already supports OO programming. Perl6 will be *fully* OO from
grounds up (but it won't force programmers to adhere to the paradigm).
How about Objective Perl?
How about Perl#?
;-)
BTW: this is a joke, isn't it?
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: Tue, 02 Nov 2004 11:01:31 +0100
From: "Vetle Roeim" <vetro@online.no>
Subject: Re: Perl is awsome!
Message-Id: <opsgt0stpc3hk3cf@quickfix.opera.com>
On Tue, 02 Nov 2004 10:57:23 +0100, Michele Dondi <bik.mido@tiscalinet.it>
wrote:
[...]
> BTW: this is a joke, isn't it?
AFAIK, Stroustrup uses groups.google.com for newsgroups (and a different
email address, at least in his latest newsgroup postings), so it probably
is. Either that, or he's had one too many down at the pub. ;-D
--
It's not a bug, it's the future.
------------------------------
Date: 02 Nov 2004 09:22:46 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <418751e5$0$11699$8b463f8a@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 2 Nov 2004 10:15:21 +0000 (UTC)
From: stratus <gis86508@cissol1.cis.nctu.edu.tw>
Subject: Regular Expression for - \C\R...
Message-Id: <cm7mno$caf$1@news.cis.nctu.edu.tw>
I want to know what is the meaning of \C and \R.
for example, if(/^\s*(\C\S+)\s+(\S+)\s+(\S+)\s+(\S+)/i)
if(/^\s*(\R\S+)\s+(\S+)\s+(\S+)\s+(\S+)\s+(\S+)/i){
I cannot find this in the document.
------------------------------
Date: 2 Nov 2004 10:29:26 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Regular Expression for - \C\R...
Message-Id: <cm7ni6$5df$1@mamenchi.zrz.TU-Berlin.DE>
stratus <gis86508@cissol1.cis.nctu.edu.tw> wrote in comp.lang.perl.misc:
> I want to know what is the meaning of \C and \R.
>
> for example, if(/^\s*(\C\S+)\s+(\S+)\s+(\S+)\s+(\S+)/i)
> if(/^\s*(\R\S+)\s+(\S+)\s+(\S+)\s+(\S+)\s+(\S+)/i){
>
>
> I cannot find this in the document.
What document? Have you looked in perlre? Search for
"In addition, Perl defines the following:".
Anno
------------------------------
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 7350
***************************************
