[31432] in Perl-Users-Digest
Perl-Users Digest, Issue: 2684 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Nov 20 06:09:42 2009
Date: Fri, 20 Nov 2009 03:09:10 -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 Fri, 20 Nov 2009 Volume: 11 Number: 2684
Today's topics:
Re: Handling two signal handler <sanjeeb25@gmail.com>
Re: Handling two signal handler <m@rtij.nl.invlalid>
Re: How to get at the perl options sharma__r@hotmail.com
Re: How to get at the perl options <marc.girod@gmail.com>
Re: How to get at the perl options sharma__r@hotmail.com
Re: How to get cell value excel in perl <justin.0908@purestblue.com>
need to do multiple SSH hops using Perl script. <deepns7@gmail.com>
need to do multiple SSH hops using Perl script. <deepns7@gmail.com>
Re: Perl to use and create PHP sessions? <sysadmin@example.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Setting text with PDF::API2 <newsojo@web.de>
Re: Setting text with PDF::API2 <bugbear@trim_papermule.co.uk_trim>
Re: sos <m@rtij.nl.invlalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 19 Nov 2009 22:10:31 -0800 (PST)
From: sanjeeb <sanjeeb25@gmail.com>
Subject: Re: Handling two signal handler
Message-Id: <198413c0-240a-4919-bc3e-db0d1e28a162@z4g2000prh.googlegroups.com>
On Nov 19, 10:24=A0pm, j...@toerring.de (Jens Thoms Toerring) wrote:
> sanjeeb <sanjee...@gmail.com> wrote:
> > I have a application which multiple modules. Each module do some task.
> > I have a signal handler defined in the main.pl which is the starting
> > point to run the application.
> > I want to define signal handler in each module which will do specific
> > task and again raised a signal which will be handled by the global
> > signal handler.
> > The signal to be caught are same throughout, not specific to any class
> > or the global handler.
> > Scenario :
> > application.pl =A0 define a a signal handler &globalhandler
> > =A0 =A0 =A0 application.pl creates a object out of foo.pm and foo.pm de=
fines
> > a handle &foo_cleaner
> > =A0 =A0 =A0 =A0when the execution is under the context of foo.pm object=
, a
>
> What do you mean with "the context of foo.pm object"?
>
> > INT signal caught. It will clean =A0 =A0up the required things populate=
d
> > by foo.pm and then raised the same signal from foo_cleaner. After
> > raising the &globalhandler should be called means the global handler
> > will be caught.
> > I tried but didnt succeded.
> > Do you have guys any idea whether there is some way out???
> > Can i get two handlers with the same signal???
>
> You can have only a single signal handler for each signal. So
> if the signal has been dealt with by foo_cleaner() then it's
> used up. Raising it again would only lead to foo_cleaner() being
> called again as long as it's still installed as the handler for
> that signal.
>
> What you can do is to simply call global_handler() from
> foo_cleaner(). You can figure out its address by inspecting
> the value of $SIG{INT} before you install foo_cleaner() as
> the new signal handler. I.e. do
>
> my $old_handler =3D $SIG{ INT };
> $SIG{ INT } =3D \&new_handler;
>
> sub new_handler {
> =A0 =A0 do_something;
> =A0 =A0 &$old_handler( @_ );}
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Regards, Jens
> --
> =A0 \ =A0 Jens Thoms Toerring =A0___ =A0 =A0 =A0j...@toerring.de
> =A0 =A0\__________________________ =A0 =A0 =A0http://toerring.de
Thanks.
I tried this before but it is not working in a threaded environment.
In context means , the object is created in a thread, but the signal
handler is installed at the
main application. Here is the flow.
./main.pl creates a thread -> object of Execution.pm is created in the
thread -> The signal handler should be installed in this context when
the thread created the object of Execution.pm.
i am hunting for the solution, let me know if you found anything,
thanks.
------------------------------
Date: Fri, 20 Nov 2009 09:09:31 +0100
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Handling two signal handler
Message-Id: <revht6-0c8.ln1@news.rtij.nl>
On Thu, 19 Nov 2009 22:10:31 -0800, sanjeeb wrote:
> I tried this before but it is not working in a threaded environment. In
> context means , the object is created in a thread, but the signal
> handler is installed at the
> main application. Here is the flow.
> ./main.pl creates a thread -> object of Execution.pm is created in the
> thread -> The signal handler should be installed in this context when
> the thread created the object of Execution.pm.
>
> i am hunting for the solution, let me know if you found anything,
> thanks.
Threads and signals don't mix, as noted in the threads documentation.
This makes Perl threads absolutely useless in my opinion. Try a fork
based solution instead.
M4
------------------------------
Date: Fri, 20 Nov 2009 00:47:42 -0800 (PST)
From: sharma__r@hotmail.com
Subject: Re: How to get at the perl options
Message-Id: <346d8c03-b3a7-4bae-8ae2-6fccd3e94b25@u16g2000pru.googlegroups.com>
On Nov 20, 5:21=A0am, "Uri Guttman" <u...@StemSystems.com> wrote:
> >>>>> "BM" =3D=3D Ben Morrow <b...@morrow.me.uk> writes:
>
> =A0 BM> Quoth sharma...@hotmail.com:
> =A0 >>
> =A0 >> Is there a way to capture the perl options in a command like this:
> =A0 >> perl -w -S script.pl
> =A0 >>
> =A0 >> @ARGV holds the options script.pl & onwards. What I want are the t=
he
> =A0 >> perl options (in this case:
> =A0 >> -w, -S ) also.
>
> =A0 BM> Some of them (like -w) show up as magic variables: see perldoc pe=
rlvar.
> =A0 BM> I don't believe that applies to -S.
>
> and a better question is why do you want them? i have never seen anyone
> ask for these in 16 years of hacking perl. what purpose could you have
> to want this info? those are options to make perl do certain things and
> there are plenty of them. also perl can use environment variables to set
> some things that options can also do. you can't tell where the settings
> came from. i smell a major XY problem here where your real problem is X
> but you are asking about your solution which is Y.
>
> uri
>
The problem that I am facing is the following: I have a perl script
(run_Calibre_Command.plx)
which i want to ensure that everybody in our team pick the identical
versions of
"perl" irrespective of his .cshrc/.tcshrc settings. Towards that end,
we use the famous
eval 'exec perl -w -S -- "$0" ${1+"$@"}'
if 0;
dictum copied from the Camel book.
But I have modified that a little & it looks somewhat like this:
:
eval '
PATH=3D/tool/all/wrappers/bin${PATH:+:}${PATH-}; export PATH
_perl_wrapper=3D"5.8.8/2007"; export _perl_wrapper
exec perl -w -S -- "$0" ${1+"$@"}
'
if 0;
use strict;
use warnings;
local $\ =3D "\n";
.....
.....
__END__
Now what is happening is that if I invoke the perl script from the
command line as:
% run_Calibre_Command.plx [script options follow here]
Then whoever uses it gets to invoke the same version of perl.
However, if I were to invoke the perl script from the command line as:
% perl [perl options] run_Calibre_Command.plx [script options
follow here]
then the eval 'exec perl ...' scheme breaks down since depending on
the user's
.cshrc/.tcshrc settings that particular version of perl binary & it's
attendant
library files get invoked. To overcome this I wrote a brief code
inside the BEGIN
block that does esentially what the eval 'exec ...' is doing.
BEGIN{
$ENV{PATH} =3D "/tool/all/wrappers/bin:$ENV{PATH}"
unless $ENV{PATH} =3D~ m{\A/tool/all/wrappers/bin[:]}xms;
if ( !exists $ENV{_perl_wrapper} || !defined $ENV{_perl_wrapper} ||
$ENV{_perl_wrapper} ne '5.8.8/2007' ) {
local ($", $\) =3D (" ", "\n");
print {*STDERR} "realigning perl path...";
$ENV{_perl_wrapper} =3D '5.8.8/2007';
exec("PATH=3D$ENV{PATH} _perl_wrapper=3D$ENV{_perl_wrapper} perl -w -
S \"@ARGV\" -- $0"); # <=3D=3D=3D=3D=3D=3D=3D=3D PROBLEM HERE
}
}
##################################
As you can see we are not able to capture the perl options using this
way as @ARGV just looks at the perl script options
not the options to perl.
In essence I just want to re-fire the perl command line as is, but
with the new perl binary.
% perl [perl options] run_Calibre_Command.plx [script options]
How would we do it, if at all it's feasible
-- Rakesh
------------------------------
Date: Fri, 20 Nov 2009 01:51:04 -0800 (PST)
From: Marc Girod <marc.girod@gmail.com>
Subject: Re: How to get at the perl options
Message-Id: <ed40d427-3300-4801-9e9a-189db545121a@x31g2000yqx.googlegroups.com>
On Nov 20, 8:47=A0am, sharma...@hotmail.com wrote:
> How would we do it, if at all it's feasible
Check that the intended perl is used, and die if not with instructions
to the user.
Is this too simple?
Marc
------------------------------
Date: Fri, 20 Nov 2009 02:55:09 -0800 (PST)
From: sharma__r@hotmail.com
Subject: Re: How to get at the perl options
Message-Id: <f896f51b-9ddd-425e-9f19-b6b48dcbdab5@y32g2000prd.googlegroups.com>
On Nov 20, 2:51=A0pm, Marc Girod <marc.gi...@gmail.com> wrote:
> On Nov 20, 8:47=A0am, sharma...@hotmail.com wrote:
>
> > How would we do it, if at all it's feasible
>
> Check that the intended perl is used, and die if not with instructions
> to the user.
>
> Is this too simple?
>
> Marc
But I dont want "perl" to die. I want it to go on thru run with the
appropriate version.
--Rakesh
------------------------------
Date: Fri, 20 Nov 2009 10:12:22 -0000
From: Justin C <justin.0908@purestblue.com>
Subject: Re: How to get cell value excel in perl
Message-Id: <69e2.4b066b86.c3f7c@zem>
On 2009-11-20, Obama <cyrusgreats@gmail.com> wrote:
> Hi good people:
> I need to get value of the cell so I can split by : and do some
> calculation,the format of numbers is like
> 12:03:20. Is there any way that I can get the value of the cell in
> perl...thanks in advance..
>
> my $workbook = Spreadsheet::WriteExcel->new($out);
You've created a new workbook, it is empty.
> my $worksheet = $workbook->add_worksheet("Result");
You have created a new worksheet in the above workbook, it too is empty.
> my $t1 = xl_rowcol_to_cell(2, 4); # E2
> my $t2 = xl_rowcol_to_cell(2, 5); # F2
$t1 now contains the string "E3" (not E2 as you state).
$t2 now contains the string "F3" (rows/cols counted from zero not one)
> my ($t1_h, $t1_min, $t1_sec) = split (/\:/, $t1);
> my ($t2_h, $t2_min, $t2_sec) = split (/\:/, $t1);
This makes no sense in light of what you have set those variables to
above.
> my $delta= $worksheet->write('G2', '=$t2_h - t1_h', $unlocked);
>
> But it doesn't work!
To read Excel files you need Spreadsheet::ParseExcel it should be
available from the same place you got Spreadsheet::WriteExcel.
In addition, the number format you've given looks like a time. Excel
stores time and date differently, in Excel it may look like 12:03:20,
but that may be down to the cell formatting, and not the actual contents
of the cell. You need to be sure that the actual cell content *is* as
you have shown, otherwise you'll not be able to split as you intend. For
example, 0.62 in a cell, with standard number formatting looks just like
that, change it to time formatting nn:nn:nn and it reads 14:57:02, but
you won't be able to split it with perl because that's not what perl
will see, it will see only 0.62. There are methods for reading the cell
formatting with perl, these may help you out if the number is stored as
I describe.
Justin.
--
Justin C, by the sea.
------------------------------
Date: Fri, 20 Nov 2009 01:57:32 -0800 (PST)
From: pradeep nair <deepns7@gmail.com>
Subject: need to do multiple SSH hops using Perl script.
Message-Id: <7dc5ddfc-5c31-453a-9aa8-661332650810@u8g2000prd.googlegroups.com>
The script must:
1. ssh to system A ,from there ssh to system B & from there ssh to
system C.
2. At system C need to connect to a DB and execute few queries and
create an output file
3. The outfile should be SCpied to Sytem A
Using command ssh -L -T, I am able to end up at System C with perl
command system. Am stuck there as in the output the cursor remains at
system C but I need the script to perform step 2 and 3 as mentioned
above.
Thanks in advance,
pRADEEP
------------------------------
Date: Fri, 20 Nov 2009 01:58:41 -0800 (PST)
From: pradeep nair <deepns7@gmail.com>
Subject: need to do multiple SSH hops using Perl script.
Message-Id: <f995c043-d1f2-498e-9677-56d508695aec@i12g2000prg.googlegroups.com>
The script must:
1. ssh to system A ,from there ssh to system B & from there ssh to
system C.
2. At system C need to connect to a DB and execute few queries and
create an output file
3. The outfile should be SCpied to Sytem A
Using command ssh -L -T, I am able to end up at System C with perl
command system. Am stuck there as in the output the cursor remains at
system C but I need the script to perform step 2 and 3 as mentioned
above.
Thanks in advance,
pRADEEP
------------------------------
Date: Thu, 19 Nov 2009 23:49:55 -0800
From: Wanna-Be Sys Admin <sysadmin@example.com>
Subject: Re: Perl to use and create PHP sessions?
Message-Id: <ESrNm.21116$gi1.9486@newsfe19.iad>
ccc31807 wrote:
> On Nov 18, 7:41 pm, Wanna-Be Sys Admin <sysad...@example.com> wrote:
>> To put it plainly, it's a centralized login, and once someone logs
>> into the main area (PHP driven), they should be able to use my
>> contributed scripts without logging in again by just following a link
>> normally, and then go back to a PHP driven area once they are done
>> (if they choose to). Ideally, if they hit my scripts first and log
>> in there, they should be able to not have to log into the PHP area
>> either.
>
> I'm not at all familiar with PHP, but have written a fair amount of
> ColdFusion and JSP. My approach to sessions is to use a database for
> the current sessions. Any script that can access the database can
> authenticate the user and validate the session (or create the new
> session).
>
> In my web apps, sessions are application wide, database driven, and
> don't depend on cookies. I've never had the problem you've described
> (but then, I don't know anything about PHP.)
>
> CC.
I'm not a big fan of PHP, I've known Perl for a long time, and PHP
wasn't popular when I was coding in Perl, so I never got into learning
yet another laguage too in depth. However, it's okay and I don't mind
it that much, I just have to reference a lot to find the same functions
in PHP as Perl, but they are similar enough where I can get into it
enough, though they might want some more involved things if I do that.
Anyway, I just can't change how it works now. They both do share the
same database, but I don't see any data stored that I could access to
verify if a session for the login is stored in the database from my
script.
I can cross reference the same login data to check against, but that's
about it, the rest use PHP sessions and Smarty, and it just makes it a
serious hassle. So, I'll just stick with having people log in/out of
my area separate, at least for the time being. It seems dumb to recode
it all in PHP just to have it in PHP, and I get the annoyance of
logging into two separate areas, even with the same credentials, but my
area is more specialized and it works without a problem and will for
years to come, so I hope they realize that and don't sweat this small
issue (I was just trying to be friendly, I don't mind trying, but in
this case it's too much of a hassle).
--
Not really a wanna-be, but I don't know everything.
------------------------------
Date: Fri, 20 Nov 2009 02:12:58 -0600
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <Z62dndhqHs0X0pvWnZ2dnUVZ_vmdnZ2d@giganews.com>
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.9 $)
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.rehabitation.com/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_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 and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: 20 Nov 2009 09:18:44 GMT
From: Oliver 'ojo' Bedford <newsojo@web.de>
Subject: Setting text with PDF::API2
Message-Id: <4b065ef4$0$6577$9b4e6d93@newsspool3.arcor-online.net>
I'm using the paragraph-function to fill text into a given box.
For most of the lines it works reasonably well, but sometimes, especially
when encountering long words (which are very common in german) paragraph
fails to word-wrap. The result are lines which extend beyond the
given box.
Is this a bug in paragraph, a feature oder am I just too stupid to use
it correctly?
Another question: what is the reference point for $txt->translate?
The left side of the baseline of the character or the upper left corner
or ...?
TIA,
Oliver
------------------------------
Date: Fri, 20 Nov 2009 09:55:23 +0000
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: Setting text with PDF::API2
Message-Id: <tdOdnTtHJqkR-pvWnZ2dnUVZ8ixi4p2d@brightview.co.uk>
Oliver 'ojo' Bedford wrote:
> I'm using the paragraph-function to fill text into a given box.
> For most of the lines it works reasonably well, but sometimes, especially
> when encountering long words (which are very common in german) paragraph
> fails to word-wrap. The result are lines which extend beyond the
> given box.
>
> Is this a bug in paragraph, a feature oder am I just too stupid to use
> it correctly?
I suspect the creator of the code didn't have words-of-German-length
in mind.
I seem to remember (from various parts of my career) that laying
out German paragraphs follows "special" rules and conventions
that aren't need or applicable to most other languages.
So - bug or limitation, depending on your viewpoint.
BugBear
------------------------------
Date: Fri, 20 Nov 2009 09:08:00 +0100
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: sos
Message-Id: <0cvht6-0c8.ln1@news.rtij.nl>
On Thu, 19 Nov 2009 18:06:33 -0800, Robin wrote:
> I was never allowed to do much of anything by our known ethereal world
> which is a secret government project or an alien race.
Ethereal is now known by the name Wireshark. Using that may solve all
your problems.
M4
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 2684
***************************************
