[28601] in Perl-Users-Digest
Perl-Users Digest, Issue: 9965 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Nov 14 06:05:35 2006
Date: Tue, 14 Nov 2006 03:05:04 -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, 14 Nov 2006 Volume: 10 Number: 9965
Today's topics:
Re: "Did not find leading dereferencer" - new findings <ro.naldfi.scher@gmail.com>
Re: "Did not find leading dereferencer" - new findings <ro.naldfi.scher@gmail.com>
Re: "Did not find leading dereferencer" - new findings <ro.naldfi.scher@gmail.com>
Re: Call graph analysis of perl source? <mark.clementsREMOVETHIS@wanadoo.fr>
Re: Loop over regexp groups anno4000@radom.zrz.tu-berlin.de
Re: Mail sending problem (reading news)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
ppm question <johngoche@gmail.com>
problems while compiling perl on solaris 10 <ashish.sarika@gmail.com>
Re: problems while compiling perl on solaris 10 anno4000@radom.zrz.tu-berlin.de
Re: reverse chomp() <shay.rozen@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 14 Nov 2006 02:40:18 -0800
From: "Ronny" <ro.naldfi.scher@gmail.com>
Subject: Re: "Did not find leading dereferencer" - new findings to an old puzzle
Message-Id: <1163500818.905253.243080@i42g2000cwa.googlegroups.com>
Peter J. Holzer schrieb:
> On 2006-11-13 12:37, Ronny <ro.naldfi.scher@gmail.com> wrote:
> > Peter J. Holzer schrieb:
> >> > The use Switch was in the code only for historic reason, and I have
> >> > removed it. I don't know of course if *this* was sufficient to make
> >> > the error go away: After all, the removal of the statement made the
> >> > code a little bit smaller, so the problem might simply have
> >> > disappeared for *this* reason (removing a comment line instead of the
> >> > use Switch would have had the same effect).
> >> Possible, but unlikely. Unless you use another module which uses
> >> Text::Balanced, you aren't calling Text::Balanced any more and hence
> >> can't get any error messages from it any more.
> > even
> > when I do a "use Switch", I never actually *write* a switch statement.
>
> That's irrelevant. The Switch module can't know whether you use a switch
> statement or not not before it has parsed your code.
May main problem was seeing *where* (at compile time) Switch.pm would
parse my code, since I thought such an attempt on parsing would have to
be done within a BEGIN block, which is not present in Switch.pm.
However I now agree with you that there indeed seems to be some parsing
going on, although it looks a bit like magic to me, and you are right
that this parsing seems to be done with the help of the module
Filter::Util::Call
(which, according to its description, is intended to write source
transformation
modules and which seems to rely on some support code written in C
- I only conclude this from the comments in its, but I must admit that
I don't
understand how that code works).
> > Then I have the impression that the error message "comes from the
> > Switch module and goes away when I remove it". I think this does not
> > describe the situation.
>
> Yes it does. Without the Switch module you get a different error
> message.
This is true, but I also get a different error message when I let the
Switch module
in my program, and - say - remove one comment line - a single, empty
comment
in the midst of a block of comment lines! This would mean that
the parsing algorithm of Switch.pm would be very sensitive to things
which
happen far away of any "interesting" or probably difficult-to-parse
constructs.
Given the observation above, that source filtering utilizes C code
(with the
notorious "buffer overflow problem" which often plagues C programmers),
I guess the right answer to the puzzle is a combination of both:
The error seems to be triggered whenever some source filtering is
active,
but the problem is not necessarily, that the code is somehow to
complicated
to parse (as you suspected - or did I misunderstand you here?), but is
more
likely related to a buffer overrun in the supporting C code - simply
because if removing "irrelevant" characters from a code (irrelevant in
the sense of the
parsing algorithm) makes a certain error go away, is very, very typical
for
buffer overrun.
> > In addition, I would like to point out that I had the same error
> > message a few months ago in a different context.
>
> Yes, I've remember the thread. You were directed towards Text::Balanced
> by somebody at the time, but you ignored that advice.
Yes, because another advice which told me to remove the prototype of a
function
definition, also made the error go away. The poster of that advice
suggested
to me that having prototypes in a bad idea in most cases anyway, and it
seemed
to me simpler to do than hunting for a Text::Balanced buried deep in
the module
nesting hierarchy (I wonder whether there is a simple way to find out
what modules
are - directly or indirectly - included in a program, and by whom ....
kind of an
"invocation graph").
Ronald
------------------------------
Date: 14 Nov 2006 02:42:19 -0800
From: "Ronny" <ro.naldfi.scher@gmail.com>
Subject: Re: "Did not find leading dereferencer" - new findings to an old puzzle
Message-Id: <1163500939.006738.250580@i42g2000cwa.googlegroups.com>
Peter J. Holzer schrieb:
> On 2006-11-13 12:37, Ronny <ro.naldfi.scher@gmail.com> wrote:
> > Peter J. Holzer schrieb:
> >> > The use Switch was in the code only for historic reason, and I have
> >> > removed it. I don't know of course if *this* was sufficient to make
> >> > the error go away: After all, the removal of the statement made the
> >> > code a little bit smaller, so the problem might simply have
> >> > disappeared for *this* reason (removing a comment line instead of the
> >> > use Switch would have had the same effect).
> >> Possible, but unlikely. Unless you use another module which uses
> >> Text::Balanced, you aren't calling Text::Balanced any more and hence
> >> can't get any error messages from it any more.
> > even
> > when I do a "use Switch", I never actually *write* a switch statement.
>
> That's irrelevant. The Switch module can't know whether you use a switch
> statement or not not before it has parsed your code.
My main problem was seeing *where* (at compile time) Switch.pm would
parse my code, since I thought such an attempt on parsing would have to
be done within a BEGIN block, which is not present in Switch.pm.
However I now agree with you that there indeed seems to be some parsing
going on, although it looks a bit like magic to me, and you are right
that this parsing seems to be done with the help of the module
Filter::Util::Call
(which, according to its description, is intended to write source
transformation
modules and which seems to rely on some support code written in C
- I only conclude this from the comments in its, but I must admit that
I don't
understand how that code works).
> > Then I have the impression that the error message "comes from the
> > Switch module and goes away when I remove it". I think this does not
> > describe the situation.
>
> Yes it does. Without the Switch module you get a different error
> message.
This is true, but I also get a different error message when I let the
Switch module
in my program, and - say - remove one comment line - a single, empty
comment
in the midst of a block of comment lines! This would mean that
the parsing algorithm of Switch.pm would be very sensitive to things
which
happen far away of any "interesting" or probably difficult-to-parse
constructs.
Given the observation above, that source filtering utilizes C code
(with the
notorious "buffer overflow problem" which often plagues C programmers),
I guess the right answer to the puzzle is a combination of both:
The error seems to be triggered whenever some source filtering is
active,
but the problem is not necessarily, that the code is somehow to
complicated
to parse (as you suspected - or did I misunderstand you here?), but is
more
likely related to a buffer overrun in the supporting C code - simply
because if removing "irrelevant" characters from a code (irrelevant in
the sense of the
parsing algorithm) makes a certain error go away, is very, very typical
for
buffer overrun.
> > In addition, I would like to point out that I had the same error
> > message a few months ago in a different context.
>
> Yes, I've remember the thread. You were directed towards Text::Balanced
> by somebody at the time, but you ignored that advice.
Yes, because another advice which told me to remove the prototype of a
function
definition, also made the error go away. The poster of that advice
suggested
to me that having prototypes in a bad idea in most cases anyway, and it
seemed
to me simpler to do than hunting for a Text::Balanced buried deep in
the module
nesting hierarchy (I wonder whether there is a simple way to find out
what modules
are - directly or indirectly - included in a program, and by whom ....
kind of an
"invocation graph").
Ronald
------------------------------
Date: 14 Nov 2006 02:46:17 -0800
From: "Ronny" <ro.naldfi.scher@gmail.com>
Subject: Re: "Did not find leading dereferencer" - new findings to an old puzzle
Message-Id: <1163501177.023820.231730@m7g2000cwm.googlegroups.com>
Peter J. Holzer schrieb:
> [Article reformatted. Please keep a consistent line length of about 70
> characters. Alternating between long and extremely short lines may be
> nice in a poem but is hard to read in prose]
Sorry, I don't do this deliberately. It is pretty difficult to do it
with the
ugly Google Groups interface (no way to display fixed font when typing,
and easy to forget a hard return at the end of the line), and
Newsoffice.de
(which is a somewhat better way to post to the Usenet) is down at the
moment.
Ronald
------------------------------
Date: Tue, 14 Nov 2006 10:33:21 +0100
From: Mark Clements <mark.clementsREMOVETHIS@wanadoo.fr>
Subject: Re: Call graph analysis of perl source?
Message-Id: <45598d60$0$5069$ba4acef3@news.orange.fr>
Roy Smith wrote:
> I have been given the "interesting" task of figuring out and documenting
> 16,000 lines perl. It's typical crud -- no comments, lots of global
> variables, etc.
>
> After poking at it for a while, it's obvious that what I need to do is
> build a call graph. Are there any tools to help me do this?
Devel::Graph ? May be a little verbose for your needs.
I've had good results with Autodia, but this builds graphs of a class
hierarchy rather than calls themselves.
Your next task will probably be refactoring: in order to do this
successfully you'll need to have automatic testing in place. Even an
application that wasn't designed for testing can be tested to some
degree at the top level using something like Test::WWW::Mechanize (if
it's a web application). If you have a well-designed barrage of
automatic tests you can be more certain (OK - less uncertain) that your
refactoring hasn't broken anything.
Mark
------------------------------
Date: 14 Nov 2006 10:28:23 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Loop over regexp groups
Message-Id: <4rtk27FsvuelU1@mid.dfncis.de>
January Weiner <january.weiner@gmail.com> wrote in comp.lang.perl.misc:
> anno4000@radom.zrz.tu-berlin.de wrote:
> > Very easy. Assuming the regex (with captures) in $re, and the string to
> > match in $_ (untested):
>
> > my @groups = m/$re/;
>
> > A regex in list context returns all its captures.
>
> Yes! That's it. Thank you so much. (very intuitive, when you think of it!)
It is. The behavior varies slightly with whether the regex has captures
and/or the /g modifier, but the variations usually do what you mean.
In fact, list assignment is the preferred method of accessing regex
captures. You avoid the special package variables $1, $2, ... and
their scoping issues. You can give the captures meaningful names,
individually or collectively. And, (your case), you don't have to
know in advance how many captures there are.
The only case where you can't avoid $1 etc. is when you need the
behavior of /g in scalar context and have captures.
Anno
------------------------------
Date: Tue, 14 Nov 2006 08:45:47 GMT
From: "Mumia W. (reading news)" <paduille.4060.mumia.w@earthlink.net>
Subject: Re: Mail sending problem
Message-Id: <%mf6h.6491$L6.2093@newsread3.news.pas.earthlink.net>
On 11/14/2006 02:23 AM, Markusin wrote:
> Hi
>
> I am trying to send a mail with perl, using as MTA ms exchange. On that
> server I need to authenticate. I wrote a small programm with following code:
>
> ######################### Begin #######################################
>
> #!/usr/bin/perl -w
>
> use Mail::Mailer;
> use MIME::Base64;
> use Authen::SASL;
>
> my $from = "markus\@empfaenger.net";
> my $to = "markus\@sender.net";
> my $subject = "markus perl probe";
> my $text = "kleine perl probe";
>
> my $args;
>
> my $type = "smtp";
> my $server = "exchange.server";
> my $smtpuser = "Markus";
> my $smtppasswd = "password";
>
> push @args, Server => $server;
> push @args, Auth => [$smtpuser, $smtppasswd];
>
> my $mailer = Mail::Mailer->new($type, @args) or die "Kann kein neues
> Mail::Mailer-Objekt erzeugen: $!\n";
>
> $mailer->open({From => $from, To => $to, Subject => $subject}) or die
> "Kann kein neues Mail::Mailer-Objekt oeffnen: $!\n";
> print $mailer $text;
> $mailer->close;
> ######################### End #######################################
>
> On executing that script I receive following error message:
>
> vajolet ~ # /home/markusin/scripts/mymailsender.pl
> Invalid argument at /usr/lib/perl5/vendor_perl/5.8.8/Mail/Mailer.pm line
> 269.
>
>
> Looking on that line in Mailer.pm :
>
> 268 # Fork and start a mailer
> 269 (defined($exe) && open($self,"|-"))
> 270 || $self->exec($exe, $args, \@to)
> 271 || die $!;
>
open($self, "|-")
attempts to fork a child of the current program, but the filehandle
would be stored in $self which is most probably an object you created
which probably won't work.
> I don't know what I am doing wrong and need your help. Do I need to pass
> a parameter, which in that script is required?
>
> Any idea what that could be?
>
> Thanks for any help
>
> Markus
--
paduille.4060.mumia.w@earthlink.net
------------------------------
Date: 14 Nov 2006 08:10:08 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <455979e0$0$81348$ae4e5890@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.7 $)
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://www.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 that they do
know and are being the "bad kind" of Lazy.
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: 14 Nov 2006 02:37:02 -0800
From: "John Goche" <johngoche@gmail.com>
Subject: ppm question
Message-Id: <1163500622.885755.204610@m7g2000cwm.googlegroups.com>
Hello,
I have ppm installed and would like to know whether
the FreezeThaw module is installed. What command
can I issue to determine whether this is the case?
Thanks,
JG
------------------------------
Date: 14 Nov 2006 01:40:27 -0800
From: "ashish" <ashish.sarika@gmail.com>
Subject: problems while compiling perl on solaris 10
Message-Id: <1163497226.824696.208880@b28g2000cwb.googlegroups.com>
Hi,
When I try to compile perl on Solaris 10, I get the following error
message :
Use which C compiler? [cc] /usr/sfw/bin/gcc
/usr/ccs/bin/as: error: unknown option '-'
/usr/ccs/bin/as: error: unknown option 't'
/usr/ccs/bin/as: error: unknown option 'aditional-format'
usage: /usr/ccs/bin/as [-V] [-Q{y,n}] [-q] [-s]
[-S] [-K {pic,PIC}] [-o objfile] [-L] [-T]
[-P [[-Yc,path] [-Ipath] [-Dname] [-Dname=def] [-Uname]]...]
[-m [-Ym,path]] [-n] [-ul] [-xF]
[-xarch={v7,v8,v8a,v8plus,v8plusa,v8plusb,v9,v9a,v9b}]
[-xcode={pic13,pic32}] file.s...
Uh-oh, the C compiler '/usr/sfw/bin/gcc' doesn't seem to be working.
/usr/ccs/bin/as: error: unknown option '-'
/usr/ccs/bin/as: error: unknown option 't'
/usr/ccs/bin/as: error: unknown option 'aditional-format'
usage: /usr/ccs/bin/as [-V] [-Q{y,n}] [-q] [-s]
[-S] [-K {pic,PIC}] [-o objfile] [-L] [-T]
[-P [[-Yc,path] [-Ipath] [-Dname] [-Dname=def] [-Uname]]...]
[-m [-Ym,path]] [-n] [-ul] [-xF]
[-xarch={v7,v8,v8a,v8plus,v8plusa,v8plusb,v9,v9a,v9b}]
[-xcode={pic13,pic32}] file.s...
Uh-oh, the C compiler '/usr/sfw/bin/gcc' doesn't seem to be working.
You need to find a working C compiler.
Either (purchase and) install the C compiler supplied by your OS
vendor,
or for a free C compiler try http://gcc.gnu.org/
I cannot continue any further, aborting.
The PATH is set as follows :
.:/bin:/usr/bin:/sbin:/usr/sbin:/usr/sfw/bin:/opt/sfw/bin:/usr/ccs/bin:/demrx/product/sybase/12.5/OCS-12_5/bin:/demrx/product/sybase/12.5/RPL-12_5/bin:/demrx/product/sybase/12.5/JS-12_5/bin:/demrx/product/sybase/12.5/ASE-12_5/bin:/demrx/product/sybase/12.5/ASE-12_5/install:/usr/bin:/etc:/bin:/usr/sbin:/sbin:/usr/ucb
The LD_LIBRARY_PATH is set as follows:
/lib:/usr/sfw/lib:/usr/lib:/demrx/product/sybase/12.5/OCS-12_5/lib:/demrx/product/sybase/12.5/OCS-12_5/lib3p64:/demrx/product/sybase/12.5/OCS-12_5/lib3p:/demrx/product/sybase/12.5/ASE-12_5/lib:
Thanks a lot for your kind help.
Ashish
------------------------------
Date: 14 Nov 2006 10:32:07 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: problems while compiling perl on solaris 10
Message-Id: <4rtk97FsvuelU2@mid.dfncis.de>
ashish <ashish.sarika@gmail.com> wrote in comp.lang.perl.misc:
> Hi,
>
> When I try to compile perl on Solaris 10, I get the following error
> message :
>
>
> Use which C compiler? [cc] /usr/sfw/bin/gcc
[...]
> Uh-oh, the C compiler '/usr/sfw/bin/gcc' doesn't seem to be working.
> You need to find a working C compiler.
> Either (purchase and) install the C compiler supplied by your OS
> vendor,
> or for a free C compiler try http://gcc.gnu.org/
> I cannot continue any further, aborting.
The diagnosis is pretty clear, isn't it?
Anno
------------------------------
Date: 14 Nov 2006 00:38:16 -0800
From: "ikeon" <shay.rozen@gmail.com>
Subject: Re: reverse chomp()
Message-Id: <1163493496.641999.25600@b28g2000cwb.googlegroups.com>
EZP wrote:
> Hi all,
> when i have a value like "max ", the chomp command will cut off
> the spaces to "max".
>
> How can i make " max" into "max"? (i need to cut the spaces from
> the begining of the word.
>
> thanks,
> EZP
You can try regex:
$test = " max";
$test =~ s/^\s*(\w*)/$1/g;
print "$test\n";
------------------------------
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 9965
***************************************
