[24512] in Perl-Users-Digest
Perl-Users Digest, Issue: 6692 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jun 15 06:05:46 2004
Date: Tue, 15 Jun 2004 03:05:05 -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, 15 Jun 2004 Volume: 10 Number: 6692
Today's topics:
dates... <raven_at@home.domonet.ru>
Re: dates... <thepoet_nospam@arcor.de>
Re: dates... <nospam@bigpond.com>
Re: HTML::Parser not stripping out comments <gisle@ActiveState.com>
Re: Kill a system process within the script <rick.cross@btopenworld.com>
Loadable object for Apache::Constants not found <visigoth@gmail.com>
Re: parsing file name assigning extension to a variable <AlexanderHeimann@yahoo.com>
Re: parsing file name assigning extension to a variable <gnari@simnet.is>
Pointer in PERL? What to use pointer expected? <timeless_illusion@yahoo.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Reasons to upgrade to latest version of Perl <rick.cross@btopenworld.com>
Re: Reasons to upgrade to latest version of Perl <thepoet_nospam@arcor.de>
SSH and Math::Pari prereq on AIX5.1 (W. Van Hooste)
Struggle with "simple" replacement (Arne)
Re: Struggle with "simple" replacement (Sam Holden)
Re: What is best module for LDAP <kkeller-usenet@wombat.san-francisco.ca.us>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 15 Jun 2004 08:27:38 +0400
From: "Sergei Shelukhin" <raven_at@home.domonet.ru>
Subject: dates...
Message-Id: <2j7c4kFuig9gU1@uni-berlin.de>
I have mysql database with datetime column PDT in the table Record. I run
the following:
my ($startdate) = $db->selectrow_array("SELECT MIN(PDT) FROM Record");
print "$startdate"; # prints out datetime ~half a hour ago from this message
post ;)
my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) =
localtime($startdate);
for my $scalar ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst)
{ print "$scalar<br />"; }
#prints out:
24
33
21
31
11
69
3
364
0
The date is ok; the values are obviously not.
What's wrong with that?
Is the date returned from selectrow statement really just a string? And if
yes, what's its workaround ( e.g. is it in the same format everywhere, on
all servers and what do I do if it is not ;) )?
------------------------------
Date: Tue, 15 Jun 2004 07:38:53 +0200
From: Christian Winter <thepoet_nospam@arcor.de>
Subject: Re: dates...
Message-Id: <40ce8b6d$0$22986$9b4e6d93@newsread2.arcor-online.net>
Sergei Shelukhin wrote:
> I have mysql database with datetime column PDT in the table Record. I run
> the following:
>
> my ($startdate) = $db->selectrow_array("SELECT MIN(PDT) FROM Record");
> print "$startdate"; # prints out datetime ~half a hour ago from this message
> post ;)
> my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) =
> localtime($startdate);
> for my $scalar ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst)
> { print "$scalar<br />"; }
>
[...]
>
> The date is ok; the values are obviously not.
Of course, but this is a mysql issue, not a perl issue. A datetime
value is, in perl's view, a string in format "YYYY-MM-DD HH:MM:SS".
You have to either parse the string from within perl, or better let
mysql do the conversion to a unix time value by calling the mysql
function "UNIX_TIMESTAMP( [datetime-value] )".
HTH
-Christian
------------------------------
Date: Tue, 15 Jun 2004 15:59:00 +1000
From: Gregory Toomey <nospam@bigpond.com>
Subject: Re: dates...
Message-Id: <1780129.Qq2HlmOjpf@GMT-hosting-and-pickle-farming>
Sergei Shelukhin wrote:
> I have mysql database with datetime column PDT in the table Record. I run
> the following:
>
> my ($startdate) = $db->selectrow_array("SELECT MIN(PDT) FROM Record");
You dont expoicitly state what format you want; it will go to some
default ...
> localtime($startdate);
... which to use to call localtime
Try using explicit formats
select date_format(min(pdt),"%e-%b-%Y %l:%i:%s %p") from record
or
select date_format(min(pdt),"%e") myday,
date_format(min(pdt),"%d") mymon,
...
from record
See http://dev.mysql.com/doc/mysql/en/Date_and_time_functions.html
gtoomey
------------------------------
Date: 15 Jun 2004 00:38:30 -0700
From: Gisle Aas <gisle@ActiveState.com>
Subject: Re: HTML::Parser not stripping out comments
Message-Id: <m3d641b79l.fsf@eik.g.aas.no>
"Jay" <boatingN.O.S.P.A.M@cox.net> writes:
> I'm trying to get HTML::Parser to strip out the comments using some of the
> sample code from the man page. I'm using the ignore_elements and I still
> get comments in the dtext. Am I doing something wrong?
Probably :)
> CODE:
> use HTML::Parser ();
>
> # Create parser object
> $p = HTML::Parser->new( api_version => 3,
> start_h => [\&start, "tagname, attr"],
> end_h => [\&end, "tagname"],
> comment_h => [\&comment, "self,text"],
> text_h => [\&dtext, "self,text"],
> marked_sections => 1,
You really want marked_sections to be enabled?
> );
>
> $p->ignore_elements( qw(script, comment, style) );
You need to remove all the "," here. Otherwise they end up part of
the strings passed to ignore_elements. Also there is no <comment> tag
in HTML, so there is not comment element either.
The extra commas probably explain why you get the JavaScript comment
reported to your &dtext callback. Anything between <script> and
</script> is reported as text. Even if it looks like a comment to you
it's not really that.
> $p->strict_comment( [1] );
I don't think you actually want strict_comment enabled either. A
plain 1 is also a perfectly fine true boolean.
> # Parse directly from file
> $p->parse_file("0");
That's a strange file name.
Regards,
Gisle
------------------------------
Date: Tue, 15 Jun 2004 08:49:00 GMT
From: Mothra <rick.cross@btopenworld.com>
Subject: Re: Kill a system process within the script
Message-Id: <0Kyzc.17589858$Of.2920267@news.easynews.com>
Mav wrote:
> The script is running on the PC.
> Once I launch the "system("Doing something take a long time");" from
> my perl script(doit.pl), I hope when the user kill my doit.pl, it will
> kill the
> "system("Doing something take a long time");" process as well, I
> really don't want leave the process behind.
>
> Is that anywhere I can find code example doing such thing?
>
Try Chapter 16 of "Perl Cookbook" published by O'Reilly - there's loads
of examples in there.
------------------------------
Date: Tue, 15 Jun 2004 08:38:57 GMT
From: "Shaheen Gandhi" <visigoth@gmail.com>
Subject: Loadable object for Apache::Constants not found
Message-Id: <BAyzc.56743$Sw.19331@attbi_s51>
Hello. I am attempting to install Bricolage along with apache, mod_perl,
and mason. I am running a gentoo system and have emerge'd apache-1.3.31 as
well as compiled in mod_perl-1.27-r4. I've installed mason and bricolage
and all their dependencies. However, when I attempt to run bric_apachectl
start (which is a bootstrap script for apache that uses a bricolage-specific
httpd.conf rather than the /etc/apache.conf), I receive an error stating
that the loadable object for Apache::Constants could not be found.
Attempting to start apache from the init script (/etc/init.d/apache start)
results in the same error. Note that running perl
/usr/lib/perl5/vendor_perl/5.8.2/i686-linux/Apache.pm does work (I get no
errors there).
I've checked the @INC for the apache and non-apache instances of running
perl and they both have the directories where Apache::Constants lives.
So, I pretty much have no idea how to fix this problem. If anyone could
help by responding to me via e-mail, that would be great.
- Shaheen
------------------------------
Date: Mon, 14 Jun 2004 22:52:46 -0700
From: Alexander Heimann <AlexanderHeimann@yahoo.com>
Subject: Re: parsing file name assigning extension to a variable
Message-Id: <r8wzc.6636$US1.3423@fed1read02>
gnari wrote:
> "Alexander Heimann" <AlexanderHeimann@yahoo.com> wrote in message
> news:1c63154d.0406141733.31ab28ca@posting.google.com...
>
>>1) My desired goal and output
>>1. open directory..
>>2. go file by file
>>3 assign extension of file to a variable @ext
>>4 assign contents of file to a variable $content
>>5 then insert content with SQL statement where PK
>>6 then do next file until end of directory
>>2) I am getting the die error output when trying to read the file. The
>>code parses the filename fine when i comment out the open file portion
>
>
> you obviously are forgetting the directory part of the
> filename when opening it
>
> gnari
>
>
>
gnari in the code below
I am using $file as the filename to open, if i comment out the open file
and read content portion i am able to parse the the file
is there a reason i can't use $file again
use File::Basename;
fileparse_set_fstype("MSDOS");
opendir (DIR, "D:/D2") or die "couldn't open directory\n";
while (defined($file = readdir(DIR))) {
($name, $dir, $ext) = fileparse($file, '\..*');
$ext =~s/^\.//;
print " dir is $dir, name is $name, extension is $ext\n";
my $input;
open($input, "<", "$file")
or die "Couldn't open file :!\n";
while(<$input>){
undef $/;
$content = <INPUT>;
print if /of/;
print $content;
}
close($input);
------------------------------
Date: Tue, 15 Jun 2004 08:41:28 -0000
From: "gnari" <gnari@simnet.is>
Subject: Re: parsing file name assigning extension to a variable
Message-Id: <camck9$qv6$1@news.simnet.is>
"Alexander Heimann" <AlexanderHeimann@yahoo.com> wrote in message
news:r8wzc.6636$US1.3423@fed1read02...
> gnari wrote:
> >
> > you obviously are forgetting the directory part of the
> > filename when opening it
> >
> gnari in the code below
> I am using $file as the filename to open, if i comment out the open file
> and read content portion i am able to parse the the file
> is there a reason i can't use $file again
[snip code where OP is forgetting the directory part]
> opendir (DIR, "D:/D2") or die "couldn't open directory\n";
here 'D:/D2' is the directory, you are reading. call this
the 'directory part'
> print " dir is $dir, name is $name, extension is $ext\n";
here is your problem. your stupid debugging. why print
a bunch of variables that have nothong to do with the problem?
they are not used in the open
> open($input, "<", "$file")
> or die "Couldn't open file :!\n";
always include the filename in the die()
or die "Couldn't open file '$file' :!\n";
if you had done this you would have seen no
directory part ('D:/D2')
gnari
------------------------------
Date: Tue, 15 Jun 2004 09:56:02 -0700
From: "Neo" <timeless_illusion@yahoo.com>
Subject: Pointer in PERL? What to use pointer expected?
Message-Id: <2j7bq1Fub78dU1@uni-berlin.de>
I'm using Win32::COM module to access an ActiveX object.
What to use where a pointer to a buffer is returned from a function???
C Declaration is as follows :
long ReadM( VARIANT * pArr );
pArr A pointer to a VARIANT that contains a pointer to a SAFEARRAY.
Here is what Documentation says :
ReadM Reads a SAFEARRAY of 8-bit integers (bytes).
The ReadM functions read a message from a channel. The entire message is
placed into a single dimensional SAFEARRAY, and a pointer to the SAFEARRAY
is returned in the parameter pArr.
Sample Visual Basic Code :-
~~~~~~~~~~~~~~~~~~~~~
Dim rtdx As Object
Dim read_array As Variant
Dim status As Long
Dim i As Integer
status = rtdx.ReadM( read_array)
If ( status = Success ) Then
For i = LBound( read_array ) to UBound( read_array )
Print read_array(i)
Next i
End If
I want to do this in PERL...
But catched in Variant, Pointer, SAFEARRAY game...!
How do I call ReadM() function and get data from it...???
Thnx!
-Neo
------------------------------
Date: Tue, 15 Jun 2004 02:22:04 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <DLGdnV03ZYkBPlPdRVn-jg@august.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, 15 Jun 2004 08:28:21 GMT
From: Mothra <rick.cross@btopenworld.com>
Subject: Reasons to upgrade to latest version of Perl
Message-Id: <Fqyzc.6640009$iA2.753837@news.easynews.com>
Can anyone give me some good reasons to upgrade Perl to the lastest
stable release? Apart from it being the latest stable release?
Unfortunately that one doesn't seem to impress managers enough to
upgrade from 5.005_03.
------------------------------
Date: Tue, 15 Jun 2004 11:42:53 +0200
From: Christian Winter <thepoet_nospam@arcor.de>
Subject: Re: Reasons to upgrade to latest version of Perl
Message-Id: <40cec49e$0$6030$9b4e6d93@newsread2.arcor-online.net>
Mothra schrieb:
> Can anyone give me some good reasons to upgrade Perl to the lastest
> stable release? Apart from it being the latest stable release?
> Unfortunately that one doesn't seem to impress managers enough to
> upgrade from 5.005_03.
IMHO you should read through "perldoc perl56delta" and
"perldoc perl58delta" to get the big view on all changes,
so you can pick out those that may be of advantage in
your environment.
HTH
-Christian
------------------------------
Date: 15 Jun 2004 02:53:02 -0700
From: wvanhooste@yahoo.com (W. Van Hooste)
Subject: SSH and Math::Pari prereq on AIX5.1
Message-Id: <495823bb.0406150153.5d7a5342@posting.google.com>
problem
I try to install Net::SSH::Perl (instead of Net::SSH). And have lots
of problems with the compilation of prereq Math::Pari and GP/PARI...
environment
I'm installing on a RS/6000 with a PPC604 processor but want to do the
same on more recent ones like POWER4 (I am using AIX 5.1).
details
No idea if the problem is GP/PARI or Math::Pari but GP/PARI returns
some incorrect values but installes, and Math::Pari failes during the
"make test"...
The AIX detection in GP/PARI does not seem to be correct. I tried
editing arch-osname and the Makefile and even tried the GP/PARI alpha
version - withouth improved results.
==> I think this should be "RS/6000" or "Power" instead of "aix"
...Processor of family `aix' detected
#### Do not know how to build for assembler `aix'. ####
#### Reversing to assembler-less type `port'. ####
#### ####
#### If you think your processor's assembler is supported ####
#### by PARI, edit libPARI/Makefile.PL and report. ####
#### ####
#### Alternatively, specify machine=YOURTYPE on the ####
#### perl Makefile.PL line ####
#### Recognized types: ####
#### alpha hppa m86k none sparcv7 sparcv8 sparcv8_micro ####
#### sparcv8_super ix86 ####
==>During compilation of Math::Pari I notice that it completely
ignores the fact i have no native C-compiler but use gcc...
cc: unrecognized option `-qmaxmem=16384'
cc: unrecognized option `-q32'
cc: unrecognized option `-qlonglong'
==>but it compiles nevertheless!
Target "all" is up to date.
...
Target "makemakerdflt" is up to date.
/usr/bin/make -- OK
==>And then we have the dissapointment...
t/00_Pari...........ok 127/127FAILED test 109
Failed 1/127 tests, 99.21% okay
t/PlotRect..........# Can't locate Term/Gnuplot.pm in @INC, ignoring
the test
skipped: Can't locate Term/Gnuplot.pm in @INC
t/analyz............ok
t/elliptic..........ok
t/graph.............# Can't locate Term/Gnuplot.pm in @INC, ignoring
plotting
t/graph.............ok, 1/28 skipped: plot() - can't test it yet
t/linear............ok
t/nfields...........ok 23/161PARI: *** Warning: insufficient
precision for f
t/nfields...........ok 156/161PARI: *** Warning: not a fundamental
discrimin
t/nfields...........ok
t/number............ok
t/objets............ok, 1/62 skipped: test producing error unsupported
yet (impo
t/ploth.............# Can't locate Term/Gnuplot.pm in @INC, ignoring
plotting
t/ploth.............ok, 10/34 skipped: various reasons
t/polyser...........ok
t/program...........ok, 13/37 skipped: various reasons
t/sumiter...........ok
t/trans.............ok
Failed Test Status Wstat Total Fail Failed List of failed
-------------------------------------------------------------------------------
t/00_Pari.t 127 1 0.79% 109
1 test and 25 subtests skipped.
Failed 1/14 test scripts, 92.86% okay. 1/823 subtests failed, 99.88%
okay.
make: The error code from the last command is 255.
Stop.
/usr/bin/make test -- NOT OK
Running make install
make test had returned bad status, won't install without force
==>I did try force install and then installation of Crypt::Random
(prereq) failed with PARI errors!
All help is welcome!
------------------------------
Date: 14 Jun 2004 21:59:11 -0700
From: kesting@gmx.net (Arne)
Subject: Struggle with "simple" replacement
Message-Id: <ff144788.0406142059.634baa73@posting.google.com>
Trying to make a simple replacement of strings I spent some hours
resulting in this:
#!/usr/bin/perl -w
#use strict;
$_ = "Just {Test4*4}";
#my $old = "{Test4*4}"; #(i) normal double quoted match
my $old = "\{Test4\*4\}"; #(ii) escaping meta chars
#my $old = '{Test4*4}'; #(iii) using single quotes
my $new = "okay";
s/$old/$new/;
print "$_\n";
It should just demonstrate how to substitute a substring containing
meta chars (e.g. { or *). I had expected that avoiding interpolation
by escaping would help. But even single quote strings aren't better.
Tell me why I am such a fool. would appreciate.
Arne
------------------------------
Date: 15 Jun 2004 05:18:56 GMT
From: sholden@flexal.cs.usyd.edu.au (Sam Holden)
Subject: Re: Struggle with "simple" replacement
Message-Id: <slrncct1m0.ids.sholden@flexal.cs.usyd.edu.au>
On 14 Jun 2004 21:59:11 -0700, Arne <kesting@gmx.net> wrote:
> Trying to make a simple replacement of strings I spent some hours
> resulting in this:
>
> #!/usr/bin/perl -w
> #use strict;
>
> $_ = "Just {Test4*4}";
> #my $old = "{Test4*4}"; #(i) normal double quoted match
> my $old = "\{Test4\*4\}"; #(ii) escaping meta chars
That doesn't escape anything. { and * are not "special" in
a double quoted string so the backslashes are essentially ignored
(or \{ is converted to { and so on).
> #my $old = '{Test4*4}'; #(iii) using single quotes
> my $new = "okay";
> s/$old/$new/;
> print "$_\n";
>
> It should just demonstrate how to substitute a substring containing
> meta chars (e.g. { or *). I had expected that avoiding interpolation
> by escaping would help. But even single quote strings aren't better.
> Tell me why I am such a fool. would appreciate.
perldoc -f quotemeta
or to do things the hard way:
"\\{Test4\\*4\\}"
or
'\{Test4\*4\}'
--
Sam Holden
------------------------------
Date: Mon, 14 Jun 2004 22:35:30 -0700
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: What is best module for LDAP
Message-Id: <2r1mac.ao2.ln@goaway.wombat.san-francisco.ca.us>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
On 2004-06-14, Robert Hazeltine <r.hazeltine@uws.edu.au> wrote:
> Any suggestions as to the best choice of a module for LDAP. A quick look
> though CPAN indicates that some of the packages are a couple of years
> old, but they still look good in that they support LDAPv3.
I've used Net::LDAP with good success.
- --keith
- --
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom
-----BEGIN xxx SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAzoqghVcNCxZ5ID8RAsjKAJ9tIckOICqVQYS3a/WDRJCqtYaPMwCbBgyo
okhUn8vSh8mVlX1ENRl2nh4=
=4C21
-----END PGP SIGNATURE-----
------------------------------
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 6692
***************************************
