[30490] in Perl-Users-Digest
Perl-Users Digest, Issue: 1733 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Jul 19 18:09:45 2008
Date: Sat, 19 Jul 2008 15:09:08 -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 Sat, 19 Jul 2008 Volume: 11 Number: 1733
Today's topics:
Re: C linked lists in Perl <sigh@gmail.com>
Re: C linked lists in Perl <m@rtij.nl.invlalid>
Re: C linked lists in Perl <m@rtij.nl.invlalid>
Re: C linked lists in Perl sln@netherlands.com
cheap shox NZ shoes PayPal <yuwenwu001@gmail.com>
Re: FAQ 4.32 How do I strip blank space from the beginn <szrRE@szromanMO.comVE>
Re: FAQ 4.32 How do I strip blank space from the beginn <brian.d.foy@gmail.com>
Re: FAQ 4.32 How do I strip blank space from the beginn sln@netherlands.com
Re: How to identify a 32 or 64 bit OS? <nospam-abuse@ilyaz.org>
new CPAN modules on Sat Jul 19 2008 (Randal Schwartz)
Re: understading double scalar variable $$ <slick.users@gmail.com>
Re: understading double scalar variable $$ <m@rtij.nl.invlalid>
Re: understading double scalar variable $$ sln@netherlands.com
Re: understading double scalar variable $$ <jurgenex@hotmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 19 Jul 2008 00:45:43 -0700
From: "Gordon Corbin Etly" <sigh@gmail.com>
Subject: Re: C linked lists in Perl
Message-Id: <6edkd8F6gsduU1@mid.individual.net>
Uri Guttman wrote:
>>>>>> "GCE" == Gordon Corbin Etly <jdhog@gmail.com> writes:
> > Uri Guttman wrote:
> >>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
> > ...
> > > > At this point you're arguing that with Lisp you have an
> > > > assembled band saw (vs. Perl's Swiss Army knife or Java's
> > > > diesel-powered hammer-screwdriver) but you can't use it until
> > > > you plug it in. Well, yeah, but that is not an argument worth
> > > > having. yeah, like arguing with brick walls over PERL vs Perl.
> > > > :)
> > My thoughts exactly. But you don't see me going around random
> > threads
> > attempting to incite a flame war, when the very problem you complain
> > about stems from your own inability to be reaonable when it comes to
> > things you have a hard view on.
> brickhead ignored. especially since you never talk perl.
Once again spilling falsehoods. Clearly you are egging this on, not only
by refusing to see any reason but by baiting in random threads. You, one
who enjoys dictating "netiquette" to others, then you turn around and
blatantly flame bait. Wonderful example you're making for others...
--
Gordon C. Etly
Email: perl -e "print q{}.reverse(q{moc.liamg@ylte.nodrog})"
------------------------------
Date: Sat, 19 Jul 2008 22:55:18 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: C linked lists in Perl
Message-Id: <pan.2008.07.19.20.55.18@rtij.nl.invlalid>
On Thu, 17 Jul 2008 17:26:58 +0000, Uri Guttman wrote:
> and i want to kill the cow-orker who said perl has no linked lists. or
> better, make him code in cobol for 10 years!
Better yet, make him implement linked lists in COBOL!
M4
------------------------------
Date: Sat, 19 Jul 2008 23:03:59 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: C linked lists in Perl
Message-Id: <pan.2008.07.19.21.03.59@rtij.nl.invlalid>
On Wed, 16 Jul 2008 18:23:44 -0400, smallpond wrote:
> The main reason for C++ was to hide pointers from your friend.
> Programmers cannot be trusted doing their own memory allocation or
> linked lists. Tell him to do what everyone else does, which is to
> attack perl on performance.
That reminds me of an old truism:
C programmers know that memory management is to important to leave it to
the OS. Perl programmers know that memory management is to important to
leave to to the programmer.
As usual, the truth is somewhere in the middle, but I would say
definitely somewhere the perl side[1].
M4
[1] In the past 5 years I had one (1!) program that did not perform well
enough in Perl. It did a lot of pack/unpack, which could be replaced by
direct member access in C. Obviously, we solved the problem by throwing
faster hardware at it.
------------------------------
Date: Sat, 19 Jul 2008 22:06:51 GMT
From: sln@netherlands.com
Subject: Re: C linked lists in Perl
Message-Id: <qvo484pr2qghp62kmqjs8tord3snm73859@4ax.com>
On Wed, 16 Jul 2008 13:11:24 -0700 (PDT), cartercc <cartercc@gmail.com> wrote:
>I guess like almost everybody, I like to discuss (argue) the merits of
>different technologies. In my world, the big two are Java and
>ColdFusion. Recently, we had someone with a background in embedded
>systems who has been advocating C. The conversation goes something
>like this:
>
>him - Does Perl have linked lists?
>me - No.
>him - Therefore, C is better than Perl because it has linked lists.
>me - But Perl has other data structures that are easier to use than
>linked lists.
>him - So what? Perl still doesn't have linked lists.
>
>I've never studied linked lists and certainly never coded one (in C or
>anything else) but it aroused my curiosity. So after searching on
>c.l.p.m. and online, I decided to see if I couldn't do a linked list
>in Perl. My first thought is to do something like this:
>
>%linked_list{$key} = { prev => $linked_list{$prev_key}{prev},
> value => $value,
> next => $linked_list{$next_key}
>{next} };
>
>I know that most people will think I'm an absolute moron for thinking
>about this (and they likely would be right), but CAN you do a linked
>list in Perl (never mind that you would never want to), and if so, how
>would you go about it?
>
>My motive is to say to my C friend, "Nya, nya, nya."
>
>Thanks, CC.
A linked list element is a Node, commonly containing a Header, that
points to the previous and next header. Within the node, below the
header, contains data.
What on earth could that be used for, and why on earth would you
need to code that?
Why would you need a linked list at all, in any language?
sln
------------------------------
Date: Sat, 19 Jul 2008 07:17:29 -0700 (PDT)
From: kjldf <yuwenwu001@gmail.com>
Subject: cheap shox NZ shoes PayPal
Message-Id: <586302a0-aa61-4e17-ad47-8978eacf45de@h17g2000prg.googlegroups.com>
cheap shox NZ shoes PayPal
welcome to shopping on www.cheapest-paypal.cn
1.5% paypal handling charge supports the online payment!
2.Use your intergla replacement more good gift!
3.notes by email and website of deliver each package at first time.
Have a good day!
Sincerely yours,
CHINASILKROAD EXPORTS CO., LTD
------------------------------
Date: Sat, 19 Jul 2008 00:49:52 -0700
From: "szr" <szrRE@szromanMO.comVE>
Subject: Re: FAQ 4.32 How do I strip blank space from the beginning/end of a string?
Message-Id: <g5s6b10p5o@news4.newsguy.com>
PerlFAQ Server wrote:
[...]
> 4.32: How do I strip blank space from the beginning/end of a string?
>
> (contributed by brian d foy)
>
> A substitution can do this for you. For a single line, you want to
> replace all the leading or trailing whitespace with nothing. You
> can do that with a pair of substitutions.
>
> s/^\s+//;
> s/\s+$//;
> You can also write that as a single substitution, although it
> turns out the combined statement is slower than the separate ones.
> That might not matter to you, though.
> s/^\s+|\s+$//g;
One might think that it would be realatively trivial to optimize a
situation like this: if all alternations are anchored, just go to the
next anchor if the previous match fails (or something to that effect.)
Does this make any sense?
--
szr
------------------------------
Date: Sat, 19 Jul 2008 14:05:27 -0500
From: brian d foy <brian.d.foy@gmail.com>
Subject: Re: FAQ 4.32 How do I strip blank space from the beginning/end of a string?
Message-Id: <190720081405275091%brian.d.foy@gmail.com>
In article <g5s6b10p5o@news4.newsguy.com>, szr <szrRE@szromanMO.comVE>
wrote:
> > s/^\s+|\s+$//g;
>
> One might think that it would be realatively trivial to optimize a
> situation like this: if all alternations are anchored, just go to the
> next anchor if the previous match fails (or something to that effect.)
>
> Does this make any sense?
Sure that makes sense. Now just make the patch and send it to p5p so I
can get back to my single regex instead of two statements :)
------------------------------
Date: Sat, 19 Jul 2008 19:52:08 GMT
From: sln@netherlands.com
Subject: Re: FAQ 4.32 How do I strip blank space from the beginning/end of a string?
Message-Id: <d8h484dgebc6rm04sj0io1els1rllc8u1b@4ax.com>
On Sat, 19 Jul 2008 14:05:27 -0500, brian d foy <brian.d.foy@gmail.com> wrote:
>In article <g5s6b10p5o@news4.newsguy.com>, szr <szrRE@szromanMO.comVE>
>wrote:
>
>> > s/^\s+|\s+$//g;
>>
>> One might think that it would be realatively trivial to optimize a
>> situation like this: if all alternations are anchored, just go to the
>> next anchor if the previous match fails (or something to that effect.)
>>
>> Does this make any sense?
>
>Sure that makes sense. Now just make the patch and send it to p5p so I
>can get back to my single regex instead of two statements :)
Yes, the special case in the engine. Check for all anchor's when parsing.
Will we start a new thread for "special cases" in the engine.
Sounds interresting, why not?
sln
------------------------------
Date: Sat, 19 Jul 2008 10:07:25 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: How to identify a 32 or 64 bit OS?
Message-Id: <g5sect$2aec$1@agate.berkeley.edu>
[A complimentary Cc of this posting was sent to
szr
<szrRE@szromanMO.comVE>], who wrote in article <g5qvsf02hgn@news4.newsguy.com>:
> > I would recommend Leon's solution instead of mine, as I am arguing
> > that the "q" template SHOULD be provided in 32-bit Perl.
> It's not 32bit Perl that doesn't 'q' - it very much does - it's whether
> or not perl was compiled with 64 bit integer *support*, for example:
>
> cd perl-5.10.0
> ./Configure -Dprefix=/usr/local/perl5.10.0 -Duse64bitint
> make && make test && make install
>
> That will set the option on by default. It will still ask you but it
> will already be on so you can just hit enter.
>
> This works perfectly fine on a 32bit Linux machine.
Nobody said anything about 32bit OSes, so it you who changed the
topic - from 32bit Perl's.
No, (without my patches) quad operations do not work in Perl even if
it has 64bit integer support. They work only if perl uses 64bit
integers for its "integer slots".
The difference is between $Config{d_longlong} (has SUPPORT for 64bit
int) and $Config{use64bitint} (USES 64bit int).
Hope this helps,
Ilya
------------------------------
Date: Sat, 19 Jul 2008 04:42:20 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Sat Jul 19 2008
Message-Id: <K48L2K.E88@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Acme-StringFormat-0.01
http://search.cpan.org/~gfuji/Acme-StringFormat-0.01/
Smart interface to sprintf()
----
Apache2-AuthenOpenID-0.07
http://search.cpan.org/~danjou/Apache2-AuthenOpenID-0.07/
OpenID authen hander for mod_perl2.
----
App-Info-0.55
http://search.cpan.org/~dwheeler/App-Info-0.55/
Information about software packages on a system
----
CPANPLUS-YACSmoke-0.01_03
http://search.cpan.org/~bingos/CPANPLUS-YACSmoke-0.01_03/
Yet Another CPANPLUS Smoke Tester
----
Catalyst-Controller-WrapCGI-0.0023
http://search.cpan.org/~rkitover/Catalyst-Controller-WrapCGI-0.0023/
Run CGIs in Catalyst
----
Catalyst-Runtime-5.7099_02
http://search.cpan.org/~mramberg/Catalyst-Runtime-5.7099_02/
Catalyst Runtime version
----
CatalystX-ListFramework-Builder-0.05
http://search.cpan.org/~oliver/CatalystX-ListFramework-Builder-0.05/
Instant AJAX web front-end for DBIx::Class, using Catalyst
----
CatalystX-ListFramework-Builder-0.06
http://search.cpan.org/~oliver/CatalystX-ListFramework-Builder-0.06/
Instant AJAX web front-end for DBIx::Class, using Catalyst
----
Class-DBI-Lite-0.002
http://search.cpan.org/~johnd/Class-DBI-Lite-0.002/
Lightweight ORM for Perl
----
Class-DBI-Lite-0.003
http://search.cpan.org/~johnd/Class-DBI-Lite-0.003/
Lightweight ORM for Perl
----
Class-DBI-Lite-0.004
http://search.cpan.org/~johnd/Class-DBI-Lite-0.004/
Lightweight ORM for Perl
----
Class-DBI-Lite-0.006
http://search.cpan.org/~johnd/Class-DBI-Lite-0.006/
Lightweight ORM for Perl
----
Devel-FindBlessedRefs-1.1.0
http://search.cpan.org/~jettero/Devel-FindBlessedRefs-1.1.0/
find all refs blessed under a package
----
Geometry-Primitive-0.04
http://search.cpan.org/~gphat/Geometry-Primitive-0.04/
Primitive Geometry Entities
----
Graphics-Primitive-0.04
http://search.cpan.org/~gphat/Graphics-Primitive-0.04/
Device and library agnostic graphics objects
----
IPC-System-Simple-0.14
http://search.cpan.org/~pjf/IPC-System-Simple-0.14/
Run commands simply, with detailed diagnostics
----
Layout-Manager-0.07
http://search.cpan.org/~gphat/Layout-Manager-0.07/
2D Layout Management
----
MooseX-Object-Pluggable-0.0008
http://search.cpan.org/~groditi/MooseX-Object-Pluggable-0.0008/
Make your classes pluggable
----
Net-Appliance-Session-1.24
http://search.cpan.org/~oliver/Net-Appliance-Session-1.24/
Run command-line sessions to network appliances
----
Net-GeoPlanet-0.1
http://search.cpan.org/~skreuzer/Net-GeoPlanet-0.1/
Access Yahoo's GeoPlanet location service
----
Net-MRIM-1.09
http://search.cpan.org/~aau/Net-MRIM-1.09/
Perl implementation of mail.ru agent protocol
----
Net-Stomp-Receipt-0.34
http://search.cpan.org/~huguei/Net-Stomp-Receipt-0.34/
An extension to Net::Stomp (STOMP client) to allow transactional sends.
----
OpenResty-0.3.16
http://search.cpan.org/~agent/OpenResty-0.3.16/
General-purpose web service platform for web applications
----
OpenResty-0.3.17
http://search.cpan.org/~agent/OpenResty-0.3.17/
General-purpose web service platform for web applications
----
POE-Component-IRC-Plugin-BaseWrap-0.006
http://search.cpan.org/~zoffix/POE-Component-IRC-Plugin-BaseWrap-0.006/
base class for IRC plugins which need triggers/ban/root control
----
Proc-ProcessTable-0.43
http://search.cpan.org/~durist/Proc-ProcessTable-0.43/
Perl extension to access the unix process table
----
Proc-UID-0.05
http://search.cpan.org/~pjf/Proc-UID-0.05/
Manipulate a variety of UID and GID settings.
----
Queue-Q4M-0.00010
http://search.cpan.org/~dmaki/Queue-Q4M-0.00010/
Simple Interface To q4m
----
Rose-DBx-Object-Renderer-0.16
http://search.cpan.org/~danny/Rose-DBx-Object-Renderer-0.16/
Web UI Rendering for Rose::DB::Object
----
SVN-Notify-2.77
http://search.cpan.org/~dwheeler/SVN-Notify-2.77/
Subversion activity notification
----
SVN-Notify-Filter-AuthZMail-1.00
http://search.cpan.org/~borlik/SVN-Notify-Filter-AuthZMail-1.00/
Determines Subversion accounts to receive the email, via the AuthZSVNAccess file
----
SVN-Notify-Filter-EmailFlatFileDB-1.00
http://search.cpan.org/~borlik/SVN-Notify-Filter-EmailFlatFileDB-1.00/
Converts account names to email address based on a flat-file database
----
Set-Object-1.23
http://search.cpan.org/~samv/Set-Object-1.23/
set of objects and strings
----
Sub-Name-0.04
http://search.cpan.org/~xmath/Sub-Name-0.04/
(re)name a sub
----
Teamspeak-0.6
http://search.cpan.org/~maletin/Teamspeak-0.6/
Interface to administrate Teamspeak-Server.
----
Text-Editor-Easy-0.34
http://search.cpan.org/~grommier/Text-Editor-Easy-0.34/
A perl module to edit perl code with syntax highlighting and more.
----
URI-ParseSearchString-2.4
http://search.cpan.org/~sden/URI-ParseSearchString-2.4/
parse Apache refferer logs and extract search engine query strings.
----
XML-Compile-0.90
http://search.cpan.org/~markov/XML-Compile-0.90/
Compilation based XML processing
----
XML-Compile-SOAP-0.74
http://search.cpan.org/~markov/XML-Compile-SOAP-0.74/
base-class for SOAP implementations
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Sat, 19 Jul 2008 11:50:51 -0700 (PDT)
From: Slickuser <slick.users@gmail.com>
Subject: Re: understading double scalar variable $$
Message-Id: <9c60651a-6bbb-4439-aa0e-5c8ddb3d9fde@l8g2000prm.googlegroups.com>
I didn't write that code sub routine.
That's why I am wondering about the dereferencing it and the if/else
statement.
But if I was to write it, it will be something like this:
use strict;
use warnings;
my $x = &parse_text(" A");
my $b = " B <-- ";
my $y = &parse_text($b);
sub parse_text()
{
my($text) = @_;
if ($text)
{
## Over ride it
$text =~ s/^\s+//;
$text =~ s/\s+$//;
}
else
{
$text = 99;
}
print "$text \n";
return $text;
}
------------------------------
Date: Sat, 19 Jul 2008 21:15:31 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: understading double scalar variable $$
Message-Id: <pan.2008.07.19.19.15.31@rtij.nl.invlalid>
On Sat, 19 Jul 2008 11:50:51 -0700, Slickuser wrote:
> I didn't write that code sub routine. That's why I am wondering about
> the dereferencing it and the if/else statement.
>
> But if I was to write it, it will be something like this:
>
> use strict;
> use warnings;
>
> my $x = &parse_text(" A");
Using & to call subroutines defeats prototypes. Don't use & unless you
are absolutely sure why you need it. This is not one of those cases.
If omitting the & raises errors, fix those errors. Don't just tag on an &
unless you khow why you need it. Again, this is not one of those cases.
>
> my $b = " B <-- ";
> my $y = &parse_text($b);
>
> sub parse_text()
Here you define a subroutine as taking no arguments, As you use the
arguments a few lines below, this is not what you want. Just omit the
parenthesis.
> {
> my($text) = @_;
> if ($text)
> {
> ## Over ride it
> $text =~ s/^\s+//;
> $text =~ s/\s+$//;
> }
> else
> {
> $text = 99;
This makes no sense.
> }
> print "$text \n";
You probably want a "my $debug=1; at the top of your program and here you
want "$debug and print "'$text'\n";
> return $text;
> }
HTH,
M4
------------------------------
Date: Sat, 19 Jul 2008 19:27:16 GMT
From: sln@netherlands.com
Subject: Re: understading double scalar variable $$
Message-Id: <v9d484pto9f1u41msl85ts9elr570esfqk@4ax.com>
On Fri, 18 Jul 2008 16:28:09 -0700 (PDT), Slickuser <slick.users@gmail.com> wrote:
>
>
>#This is the correct of calling the subroutine?
>&parse_text(" A");
>#$text will be "A"
>
>Isn't that how you define a sub routine? sub parse_text() { }
>
>
Not sure if this is a protoype question, sub call question or ref question.
To figure out usage, reference can be decoded with the ref() function.
Checking that, you can see what the Perl reference types can be.
Setting aside prototype, the parse_text sub appears to strip white space from start/end of a string.
There are many levels of error checking, and there are good coding practices that
can help when the code is revisited in the future, and out of necessity would be appropriate.
>sub parse_text()
>{
> my($text) = @_;
> if ($text)
> {
> $$text =~ s/^\s+//;
> $$text =~ s/\s+$//;
> }
> else
> {
> s/^\s+//;
> s/\s+$//;
> }
>
>}
Appropriate naming of functions, relavent to what they do.
Operating on $_ inside a sub based on its external value is bad, expecially within an
else block.
If a user were to be the caller of this function, more error checking would be better.
sub parse_text
{
my $text = @_;
if (defined $text) {
if (ref($text) eq 'SCALAR') {
print "SCALAR ref\n");
}
elsif (ref(\$text) eq 'SCALAR') {
print "SCALAR string\n");
$text = \$text;
}
elsif (ref($text) eq 'GLOB' || ref(\$text) eq 'GLOB') {
print "GLOB ref or Filehandle\n";
$text = undef;
}
elsif (ref($text) eq 'CODE') {
print "CODE ref\n";
$text = undef;
}
if (defined $text) {
$$text =~ s/^\s+//;
$$text =~ s/\s+$//;
print "No problem\n";
return 1;
}
}
print "Nothing to do\n";
return 0;
}
This is all optional though.
sln
------------------------------
Date: Sat, 19 Jul 2008 19:47:04 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: understading double scalar variable $$
Message-Id: <lhg484tckijupqnlivsrc6u37u3taqc9vn@4ax.com>
Slickuser <slick.users@gmail.com> wrote:
>I didn't write that code sub routine.
You didn't write _WHAT_ code sub routine? It is customary to quote
enough context such that a posting makes sense on it's own.
[...]
>my $x = &parse_text(" A");
[...]
>my $y = &parse_text($b);
Why are you overriding the prototype and calling parse_text with & and
an argument when ...
>sub parse_text()
... the definition of parse_text explicitely(!) declares that the sub
does _NOT_ take any argument ...
> my($text) = @_;
... only to extract the non-existing argument as its first action?
That is nuts!
jue
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 1733
***************************************
