[26181] in Perl-Users-Digest
Perl-Users Digest, Issue: 8370 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Aug 30 06:05:33 2005
Date: Tue, 30 Aug 2005 03:05:06 -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, 30 Aug 2005 Volume: 10 Number: 8370
Today's topics:
Re: Calculation with DATEs <simon@unisolve.com.au>
Can I Force Perl to Bypass File Write Buffers? <hal@thresholddigital.com>
Re: Can I Force Perl to Bypass File Write Buffers? <simon@unisolve.com.au>
Re: Can I Force Perl to Bypass File Write Buffers? (Anno Siegel)
comparing 2 arrays <sppNOSPAM@libello.com>
Re: comparing 2 arrays (Anno Siegel)
Re: comparing 2 arrays <sppNOSPAM@libello.com>
file not found in DBD::Oracle <krispin27@hotmail.com>
Re: MJD HOP influence (Anno Siegel)
Net::POP3 with SSL <kak@purdue.edu>
Re: Net::POP3 with SSL <michael.kebe@NOSPAM.COM>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Template-Toolkit-2.14 fails make on FC3 <usenet@NOSPAM.obantec.net>
Re: Wrote a eBayAPI perl module, how to release it to C <ignoramus23186@NOSPAM.23186.invalid>
Re: Wrote a eBayAPI perl module, how to release it to C (Anno Siegel)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 30 Aug 2005 17:07:21 +1000
From: Simon Taylor <simon@unisolve.com.au>
Subject: Re: Calculation with DATEs
Message-Id: <df10ps$ut7$1@otis.netspace.net.au>
Dietmar Kehr wrote:
>
> I need a procedure for calculations with dates,
> e.g. let
> $date1= 22 June 1960
> $date2= 29 August 2004
> then i would appreciate a procedure that calculates
> the time-difference from $date1 until $date2 and such things.
>
> Are there data-formats for dates and such
> procedures? Where do I find them?
See:
http://www.perlmeme.org/faqs/datetime/comparing_dates.html
and
http://www.perlmeme.org/faqs/datetime/datetime_overview.html
Regards,
Simon Taylor
--
www.perlmeme.org
------------------------------
Date: Tue, 30 Aug 2005 02:45:44 -0400
From: Hal Vaughan <hal@thresholddigital.com>
Subject: Can I Force Perl to Bypass File Write Buffers?
Message-Id: <jM6dnSLSxvEEnYneRVn-tQ@comcast.com>
I'm using Perl 5.6.1 (and in some cases 5.8) on Linux. I've noticed that
when I'm processing files, that Perl writes in blocks, so it'll process a
number of items, and instead of the file having one line at a time written
to it, it'll get a whole block at once suddenly written to the disk.
Is there any way to avoid this and force Perl to write each line as I use a
"print" statement to output the line? I log (in MySQL) each item as I
finish it, so if power fails or the program is aborted, the system can pick
up right where it left off. Because of the buffers, the log is ahead of
what is written to the file, which would mean I'd lose the data between
what's written and what's logged.
Thanks!
Hal
------------------------------
Date: Tue, 30 Aug 2005 17:01:57 +1000
From: Simon Taylor <simon@unisolve.com.au>
Subject: Re: Can I Force Perl to Bypass File Write Buffers?
Message-Id: <df10fo$ups$1@otis.netspace.net.au>
Hal Vaughan wrote:
> I'm using Perl 5.6.1 (and in some cases 5.8) on Linux. I've noticed that
> when I'm processing files, that Perl writes in blocks, so it'll process a
> number of items, and instead of the file having one line at a time written
> to it, it'll get a whole block at once suddenly written to the disk.
>
> Is there any way to avoid this and force Perl to write each line as I use a
> "print" statement to output the line?
You'll need to disable buffering by setting $| to non-zero.
See $| in
perldoc perlvar
and also checkout
perldoc -f select
This sample should do what you want:
#!/usr/bin/perl
use strict;
use warnings;
open (OUTPUT, '>', 'sample') or die "Could not create file: $!";
my $fd = select(OUTPUT);
$| = 1;
select($fd);
for (0..20) {
print OUTPUT "some data...\n";
sleep 2;
}
close OUTPUT;
Regards,
Simon Taylor
--
www.perlmeme.org
------------------------------
Date: 30 Aug 2005 09:12:02 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Can I Force Perl to Bypass File Write Buffers?
Message-Id: <df17t2$99q$2@mamenchi.zrz.TU-Berlin.DE>
Simon Taylor <simon@unisolve.com.au> wrote in comp.lang.perl.misc:
> Hal Vaughan wrote:
> > I'm using Perl 5.6.1 (and in some cases 5.8) on Linux. I've noticed that
> > when I'm processing files, that Perl writes in blocks, so it'll process a
> > number of items, and instead of the file having one line at a time written
> > to it, it'll get a whole block at once suddenly written to the disk.
> >
> > Is there any way to avoid this and force Perl to write each line as I use a
> > "print" statement to output the line?
>
> You'll need to disable buffering by setting $| to non-zero.
[good advice snipped]
Just one note: "$| = 1" doesn't disable buffering, it enables auto-flushing.
The buffer(s) remain in place and active, but after each print-statement
the buffer is automatically emptied (presumably into the next buffer down
the line). You still have character buffering (and you want it).
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
------------------------------
Date: Tue, 30 Aug 2005 10:10:06 +0200
From: =?ISO-8859-1?Q?S=E9bastien_Cottalorda?= <sppNOSPAM@libello.com>
Subject: comparing 2 arrays
Message-Id: <4314145b$0$12784$636a15ce@news.free.fr>
Hi all,
I have those two arrays:
@estimated = qw ( 1 3 6 7 3 1 2 4 6 9);
@arrived = qw ( 6 7 1 0 4);
I need to determine the next value that will probably come in the
@arrived array.
As you can see, I can have some "polution" in the @arrived array (with
the 0 value that should not have occured, but we need to to with that).
I need an algorithm that can give me the probably next value => 6
It smells a 2 arrays comparaison, but ...
How can I manage to do that.
Is someone have a clue ?
Thanks in advance for any kind of help.
Sebastien
------------------------------
Date: 30 Aug 2005 09:02:12 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: comparing 2 arrays
Message-Id: <df17ak$99q$1@mamenchi.zrz.TU-Berlin.DE>
Sébastien Cottalorda <sppNOSPAM@libello.com> wrote in comp.lang.perl.misc:
> Hi all,
>
> I have those two arrays:
>
> @estimated = qw ( 1 3 6 7 3 1 2 4 6 9);
> @arrived = qw ( 6 7 1 0 4);
You have formatted @arrived so that corresponding elements appear under
their counterparts in @estimated, but without such an indication
it will be hard to establish the relation.
> I need to determine the next value that will probably come in the
> @arrived array.
> As you can see, I can have some "polution" in the @arrived array (with
> the 0 value that should not have occured, but we need to to with that).
What about the missing values in @arrived? Are there supposed to be
undefined entries in the @arrived array in their place, or are they
just missing?
> I need an algorithm that can give me the probably next value => 6
> It smells a 2 arrays comparaison, but ...
If you want help with the algorithm you'll have to explain the relation
of the @estimated and the @arrived arrays in more detail. All we know
now is that some elements in @arrived may or may not be equal to elements
of @estimated. That is not enough information to base an algorithm on.
> How can I manage to do that.
Walking through two arrays in parallel is usually done using an index
(untested):
use Scalar::Util 'min';
for ( 0 .. min $#estimated, $#arrived ) {
# compare $estimated[ $_] with $arrived[ $_]
}
> Is someone have a clue ?
Not yet. If you give us a clue what you really want to accomplish,
someone may.
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
------------------------------
Date: Tue, 30 Aug 2005 11:42:27 +0200
From: =?ISO-8859-1?Q?S=E9bastien_Cottalorda?= <sppNOSPAM@libello.com>
Subject: Re: comparing 2 arrays
Message-Id: <431429ff$0$18588$636a15ce@news.free.fr>
Anno Siegel a écrit :
> Sébastien Cottalorda <sppNOSPAM@libello.com> wrote in comp.lang.perl.misc:
>
>>Hi all,
>>
>>I have those two arrays:
>>
>>@estimated = qw ( 1 3 6 7 3 1 2 4 6 9);
>>@arrived = qw ( 6 7 1 0 4);
The real situation is that:
I work in the public car park of monaco (about 30 car parks).
A customer of mine, on internet, can plan a route that he want to do.
1st : Go to car park n°1
2nd : Go to car park n°3
3rd : Go to car park n°6
...
it represents @estimated array.
But when he comes in monaco, he finally decides to come first to car
park n°6, then car park n°7, then car park n°1, ... and car park n°4.
It represents @arrived array.
I need, when he want to exit a car park, to ask him if he plan to go to
the next car park n°....
In that precise case : I need to program an algorithm that give me '6'.
I smell now a recursive function.
First check the 6 (first element in @arrived) in @estimated.
Foreach position found, try to find now the 7 ...
Sebastien
------------------------------
Date: Tue, 30 Aug 2005 09:21:18 +0200
From: Perico el de los palotes <krispin27@hotmail.com>
Subject: file not found in DBD::Oracle
Message-Id: <df11al$mn71@news.hi.inet>
I've tried to installl a DBD:Oracle Module in a HP-UX B.11.00 a 900/778
whit a perl 5.8.0 version
"Configuring DBD::Oracle ...
>>> Remember to actually *READ* the README file!
Especially if you have any problems.
Using Oracle in /opt/oracle/home8.1.6
DEFINE _SQLPLUS_RELEASE = "801060000" (CHAR)
Oracle version 8.1.6.0 (8.1)
Unable to locate an oracle.mk, proc.mk or other suitable *.mk
file in your Oracle installation. (I looked in
/opt/oracle/home8.1.6/rdbms/lib/oracle.mk
/opt/oracle/home8.1.6/rdbms/demo/oracle.mk
/opt/oracle/home8.1.6/rdbms/demo/demo_rdbms.mk
/opt/oracle/home8.1.6/otrace/demo/atmoci.mk
/opt/oracle/home8.1.6/precomp/demo/proc/proc.mk
/opt/oracle/home8.1.6/precomp/demo/proc/demo_proc.mk
/opt/oracle/home8.1.6/proc/lib/proc.mk
/opt/oracle/home8.1.6/proc16/lib/proc16.mk)
The oracle.mk (or demo_rdbms.mk) file is part of the Oracle
RDBMS product. The proc.mk (or demo_proc.mk) file is part of
the Oracle Pro*C product. You need to build DBD::Oracle on a
system which has one of these Oracle components installed.
(Other *.mk files such as the env_*.mk files will not work.)"
I've looking for this files in my machine but I haven't found it.
After, I've looking for this files in the Oracle Distribution and I
haven't found either
Can anyone help me please ???? Cna anyone tell me what can I do ??
Thanks . . . . a lot
------------------------------
Date: 30 Aug 2005 08:44:56 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: MJD HOP influence
Message-Id: <df16a8$8j9$1@mamenchi.zrz.TU-Berlin.DE>
Matija Papec <perl@my-header.org> wrote in comp.lang.perl.misc:
> X-Ftn-To: Anno Siegel
>
> anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) wrote:
> >> It seems that functional approach is better suited for smaller "classes"
> >> compared to classical OOP.
> >
> >With "functional approach", do you mean a class whose objects are
> >coderefs? What is the "classical" approach and what are the advantages
> >you see?
>
> By classic OO perl I mean using package and blessing hash/array/etc into it.
That's what I mean too.
> Potential advantage is avoiding separate file/package when you only need a
> few methods for your objects.
Avoiding a separate *file* is usually just a matter of source organization,
it can be done with any implementation. Avoiding a *package* goes to
the root of Perl OO since classes are normally packages. So the question
is, what takes the role of classes in this implementation? I sincerely
don't see what does.
> > The hallmark of Perl OO is that objects
> >are blessed into their class. This never happens here. Neither are the
>
> True, but nobody claimed otherwise..
Then please explain the terms: What are objects in this implementation,
what are methods and what are classes. I can't think of an OO system
that doesn't define these.
I haven't read HOP cover to cover yet. Perhaps you could point out
what part of the book stimulated your code so others can read up on
the background.
> > $obj->(addcond => [id => 7]);
> >
> >etc. method calls, this is just the syntax to call a coderef. So whatever
> >you have built, it isn't an alternative to a classical OO approach.
>
> That depends on what do you mean it should provide to be an alternative.
> This example has *some* OO qualities like object methods and inheritance; in
> that way it follows OO paradigm (OO paradigm in general, not that of perl).
What are the object methods, and what are objects, and how does
inheritance happen? Normally inheritance goes from one class to another.
Without defining what classes are, it is impossible to even talk about
inheritance.
> >Otherwise, classes whose objects are coderefs offer better protection
> >(and harder access to) the the object variables, assuming that the
> >object variables are implemented as private lexicals. They are usually
> >harder to deal with than more conventional implementations. The size
>
> Yes; unfortunately I'm not sure if you can inherit from such class; perhaps
> building parent so it can provide data container for it's children?
With a standard implementation of a Perl class with objects that happen
to be coderefs, inheritance happens like with any other Perl class.
As usual in Perl OO, it depends on the implementation of the base
class whether inheritance is easy, hard or impossible. There is
nothing fundamentally different from classes whose objects are (say)
hashrefs.
> >of the class (in terms of number and complexity of methods) has little
> >to do with the advantages and drawbacks of this approach.
>
> Now that you mention this, I can only say that my OO coderefs doesn't suffer
> completely like blessed ones. :)
Sorry, I don't understand this sentence.
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
------------------------------
Date: Tue, 30 Aug 2005 06:27:50 GMT
From: Avi Kak <kak@purdue.edu>
Subject: Net::POP3 with SSL
Message-Id: <tvu7h1h2ri9mi72o72m07nl5md3cetcuu0@4ax.com>
Hello:
Is there a version of the Net::POP3 module that works with SSL but
has essentially the same interface?
Any help would be much appreciated. Thanks.
Avi Kak (kak@purdue.edu)
------------------------------
Date: Tue, 30 Aug 2005 11:59:56 +0200
From: Michael Kebe <michael.kebe@NOSPAM.COM>
Subject: Re: Net::POP3 with SSL
Message-Id: <43142e31$0$2106$9b4e6d93@newsread2.arcor-online.net>
Avi Kak schrieb:
> Is there a version of the Net::POP3 module that works with SSL but
> has essentially the same interface?
I found a Mail::POP3Client at search.cpan.org. Looks like it supports SSL.
Michael
------------------------------
Date: 30 Aug 2005 07:22:23 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <4314092e$0$4860$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, 30 Aug 2005 07:08:36 +0100
From: "Mark D Smith" <usenet@NOSPAM.obantec.net>
Subject: Re: Template-Toolkit-2.14 fails make on FC3
Message-Id: <4313f81b$0$25089$db0fefd9@news.zen.co.uk>
"Mark D Smith" <usenet@NOSPAM.obantec.net> wrote in message
news:4310230a$0$3295$da0feed9@news.zen.co.uk...
> Hi
>
> perl Makefile.PL
> make (using all defaults)
>
> fails
>
> Failed 2/90 test scripts, 97.78% okay. 2/2596 subtests failed, 99.92%
okay.
> make: *** [test_dynamic] Error 255
>
> so i found an rpm an used yum
>
> yum install perl-Template-Toolkit-2.14-1.1.fc3.rf.i386
>
> <snip Processing Dependency output>
>
<snip>
> Yet i can see all the GD files in /usr/lib/perl5/site_perl/5.8.5/GD/Graph
>
> what have i overlooked and why did yum not grab the Dependencies
>
> Mark
>
I have fixed the issue with the help of a member on the template-toolkit
list. (Thanks Dave).
replaced the yum.conf with the one from http://www.fedorafaq.org/fc3/ and it
finds the extras and installed all required parts and now it works.
Mark
------------------------------
Date: Tue, 30 Aug 2005 05:22:40 GMT
From: Ignoramus23186 <ignoramus23186@NOSPAM.23186.invalid>
Subject: Re: Wrote a eBayAPI perl module, how to release it to CPAN?
Message-Id: <A2SQe.97283$9j.30060@fe19.usenetserver.com>
Thanks, I just created a distro and submitted it to cpan.
i
On Mon, 29 Aug 2005 19:24:40 -0700, Jim Gibson <jgibson@mail.arc.nasa.gov> wrote:
> In article <41PQe.110808$f24.52815@fe18.usenetserver.com>,
> Ignoramus23186 <ignoramus23186@NOSPAM.23186.invalid> wrote:
>
>> On 30 Aug 2005 01:32:32 GMT, John Bokma <john@castleamber.com> wrote:
>> > Ignoramus23186 <ignoramus23186@NOSPAM.23186.invalid> wrote:
>> >
>> >> On 29 Aug 2005 21:22:01 GMT, John Bokma <john@castleamber.com> wrote:
>> >
>
> [snip]
>
>> >
>> >> How do I make it into a nice CPAN distro?
>> >
>> ><http://cpan.org/misc/cpan-faq.html#How_contribute_modules>
>> >
>> > I seem to remember that h2xs has an option to make a directory structure
>> > and the necessary initial files which is often used to make CPAN distros.
>> > (I.e. the README, INSTALL, etc. Note that you have to edit several of those
>> > files)
>> >
>>
>> What I recall is that there is a super nice system for making
>> Makefile.PL and whatnot, make test etc. Unfortunately, I forgot the
>> name of that system.
>
> See 'perldoc perlnewmod' and 'perldoc module-starter' for information
> on the module-starter utility.
>
>
> http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
--
------------------------------
Date: 30 Aug 2005 09:37:01 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Wrote a eBayAPI perl module, how to release it to CPAN?
Message-Id: <df19bt$99q$3@mamenchi.zrz.TU-Berlin.DE>
Ignoramus23186 <ignoramus23186@NOSPAM.23186.invalid> wrote in comp.lang.perl.misc:
> I am looking for helpful (as opposed to unhelpful) replies.
Thanks for telling us.
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
------------------------------
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 8370
***************************************
