[28520] in Perl-Users-Digest
Perl-Users Digest, Issue: 9884 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 24 06:05:36 2006
Date: Tue, 24 Oct 2006 03:05:05 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 24 Oct 2006 Volume: 10 Number: 9884
Today's topics:
Archive::Zip - how can I recover to write protected fil <lev.weissman@creo.com>
Re: Automatic login to a web page <jagjeet.malhi@gmail.com>
Re: c like structure in Perl <josef.moellers@fujitsu-siemens.com>
Re: c like structure in Perl <quetzalcotl@consultant.com>
Re: c like structure in Perl <peace.is.our.profession@gmx.de>
Re: c like structure in Perl <rvtol+news@isolution.nl>
Re: Can't find string terminator ... <bik.mido@tiscalinet.it>
Re: Can't find string terminator ... <bik.mido@tiscalinet.it>
Failed to install mod_perl <bol@adv.magwien.gv.at>
Re: FAQ 4.18 Does Perl have a Year 2000 problem? Is Per <ebohlman@omsdev.com>
Re: File and directory permissions <ismael.pernas.c@gmail.es>
Re: I have no problems eating cereal...after it softens <zen13097@zen.co.uk>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: question about using jpegtran for lossless compress <bugbear@trim_papermule.co.uk_trim>
Re: Scripting an EXE <bik.mido@tiscalinet.it>
Re: string substitution for a file, without replacing p <bik.mido@tiscalinet.it>
Re: Why I no longer use Perl <bik.mido@tiscalinet.it>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 24 Oct 2006 00:13:18 -0700
From: "MoshiachNow" <lev.weissman@creo.com>
Subject: Archive::Zip - how can I recover to write protected files/folders ?
Message-Id: <1161673998.299687.98550@k70g2000cwa.googlegroups.com>
HI,
Using Archive::Zip - how can I recover to write protected files/folders
,meaning unzip overwriting them ?
Thanks
------------------------------
Date: 24 Oct 2006 01:59:14 -0700
From: "Jagjeet_Singh" <jagjeet.malhi@gmail.com>
Subject: Re: Automatic login to a web page
Message-Id: <1161680354.178983.195120@f16g2000cwb.googlegroups.com>
Hi David,
Thanks for your reply, Actually I was looking for any perl script which
can be run
in background.
Regards,
Js
usenet@DavidFilmer.com wrote:
> Jagjeet_Singh wrote:
> > [ a question about automating browser logins]
>
> To CLPMisc: At first, when I read the OP's question, I thought, "no
> way," but I got to wondering...
>
> Would it be possible to use WWW::Mechanize (via a program in the
> startup group) to obtain a cookie and put it in a directory which just
> happened to also be the browser's cookie jar, and thus have the session
> pre-authenticated when the browser starts up? That would be kinda
> cool...
>
> --
> David Filmer (http://DavidFilmer.com)
------------------------------
Date: Tue, 24 Oct 2006 09:15:55 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: c like structure in Perl
Message-Id: <ehkemr$sdu$1@nntp.fujitsu-siemens.com>
adarsh.hrbr@gmail.com wrote:
> Hi all,
>=20
> I have written a socket program whose Client is in Perl and the
> Server is in C. To some extent I was successful in obtaining the data
> and printing the same. But my server (UDP ) has some structures . The
> data pertaining to these structures are to be communicated from the
> Perl client. I thought using hash in Perl could be to solution, but
> what I am sceptical about is; will I be able to typecast the same in c
> to obtain the data?
>=20
> Below is a structure in c which I want to type cast. Can somebody
> suggest a method to define this in Perl so that I can typecaste the
> same in my Server to obtain the data.
>=20
> typedef struct {
>=20
> uint8 Reserved;
> uint32 ipaddr;
> uint32 netmask;
> uint16 command;
>=20
> } sample;=20
>=20
> uint - unsigned int type - 8,16 and 32 bytes - in length
The only thing I can come up is pack/unpack.
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: 24 Oct 2006 01:43:41 -0700
From: "Ingo Menger" <quetzalcotl@consultant.com>
Subject: Re: c like structure in Perl
Message-Id: <1161679421.178038.37760@k70g2000cwa.googlegroups.com>
adarsh.hrbr@gmail.com wrote:
> Hi all,
>
> I have written a socket program whose Client is in Perl and the
> Server is in C. To some extent I was successful in obtaining the data
> and printing the same. But my server (UDP ) has some structures . The
> data pertaining to these structures are to be communicated from the
> Perl client. I thought using hash in Perl could be to solution, but
> what I am sceptical about is; will I be able to typecast the same in c
> to obtain the data?
>
> Below is a structure in c which I want to type cast. Can somebody
> suggest a method to define this in Perl so that I can typecaste the
> same in my Server to obtain the data.
>
> typedef struct {
>
> uint8 Reserved;
> uint32 ipaddr;
> uint32 netmask;
> uint16 command;
>
> } sample;
>
> uint - unsigned int type - 8,16 and 32 bytes - in length
perldoc -f pack
Note that between any two fields of the struct the C compiler may have
inserted some padding.
------------------------------
Date: Tue, 24 Oct 2006 10:40:16 +0200
From: Mirco Wahab <peace.is.our.profession@gmx.de>
Subject: Re: c like structure in Perl
Message-Id: <ehkjpp$p7g$1@mlucom4.urz.uni-halle.de>
Thus spoke adarsh.hrbr@gmail.com (on 2006-10-24 06:57):
> Below is a structure in c which I want to type cast. Can somebody
> suggest a method to define this in Perl so that I can typecaste the
> same in my Server to obtain the data.
>
> typedef struct {
>
> uint8 Reserved;
> uint32 ipaddr;
> uint32 netmask;
> uint16 command;
>
> } sample;
>
As Josef said, you have to build a 'unpack'
format and unpack the struct parts into
variables. I did this sometimes and your
example seems easy enough to make some
example of it:
...
sample s; /* your sample from above */
char* c;
printf("my $c_strct = read_record();\nmy $fmt = \"");
printf("C"); /* Reserved */
for(c=(char*)&s.Reserved+1; c<(char*)&s.ipaddr; c++) printf("x");
printf("L"); /* ipaddr */
for(c=(char*)&s.ipaddr+4; c<(char*)&s.netmask; c++) printf("x");
printf("L"); /* netmask */
for(c=(char*)&s.netmask+4; c<(char*)&s.command; c++) printf("x");
printf("S"); /* command */
for(c=(char*)&s.command+2; c<(char*)&s+sizeof(s); c++) printf("x");
printf("\";\nmy ($Reserved, $ipaddr, $netmask, $command) = unpack($fmt, $c_strct);\n");
...
(I hope I got this right and made not too much mistakes here ;-)
If you have 'encoded' your ip or netmask in some way (sequence of 4 IPV4-bytes)
you have to decode that $ipaddr (long) by unpacking it again (unpack "CCCC", $ipaddr)
to get the 4 numbers out, same with netmask.
But I'm sure there are some Modules for this too -- but you see the picture?
Regards
Mirco
------------------------------
Date: Tue, 24 Oct 2006 11:48:06 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: c like structure in Perl
Message-Id: <ehkuk6.1cc.1@news.isolution.nl>
adarsh.hrbr@gmail.com schreef:
> Below is a structure in c which I want to type cast. Can somebody
> suggest a method to define this in Perl so that I can typecaste the
> same in my Server to obtain the data.
>
> typedef struct {
>
> uint8 Reserved;
> uint32 ipaddr;
> uint32 netmask;
> uint16 command;
>
> } sample;
>
> uint - unsigned int type - 8,16 and 32 bytes - in length
The sizeof(sample) doesn't need to be 11. If not, use 'offsetof(s,m)',
or subtract pointers, to find out where the members are in the struct.
See also #pragma pack().
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: 24 Oct 2006 11:21:49 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Can't find string terminator ...
Message-Id: <2nmrj2hhsef6dm6716v09slejn9dnu609g@4ax.com>
On Mon, 23 Oct 2006 16:42:52 -0400, Amer Neely
<softouch@softouch.on.ca> wrote:
>> You're sure there is a newline after EndOfText?
>>
>> Might be that you have accidently pressed a key combination that inserts a
>> hidden character in your terminator. I would delete EndOfText (twice), and
>> type it in again (once), and copy it.
>>
>
>Believe me, I've tried everything I can think of to ensure there is
>nothing else on that line except the newline at the end. There is
>something very strange going on here.
Not to distrust you, but what about cat -A?
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 24 Oct 2006 11:24:16 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Can't find string terminator ...
Message-Id: <0rmrj2tjfsl5v7qu0brjpitjlam4e10qm7@4ax.com>
On Mon, 23 Oct 2006 19:01:19 -0400, Amer Neely
<softouch@softouch.on.ca> wrote:
>In TextPad my default font was verdana. I switched that to courier. Then
>copied the code from my test.pl file. Deleted that file, then into a new
>file I pasted the code, but now in the new font. Voila. Unbelievable but
>true.
Indeed unbelievable: I don't know TP, but the font used for rendering
should have nothing to do with one file's actual contents...
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Tue, 24 Oct 2006 09:12:39 +0200
From: "Ferry Bolhar" <bol@adv.magwien.gv.at>
Subject: Failed to install mod_perl
Message-Id: <1161673962.573155@proxy.dienste.wien.at>
Hi,
I tried to install mod_perl 2.0.2 on a system running Apache 2.0.59.
The final link operation fails with
ld:
Invalid flag usage:
Wl,-rpath,/usr/lib/perl-5.8.0/lib/5.8.0/alpha-dec_osf/CORE,
-Wx,-option must appear after -_SYSTYPE_SVR4
ld: Usage: ld [options] file [...]
*** Exit 1
Stop.
Exit 1
The OS is Tru64 (Digital UNIX) 5.1B on an AlphaServer DS25.
I could install Apache 2.0.59 without problems.
Has anyone experience with a configuration like this?
BTW: is there a documentation about the Apache 2.0 API
(the successor of the O'Reilly 'eagle book')?
Thanks for your help,
Ferry
--
Ing Ferry Bolhar
Magistrat der Stadt Wien - MA 14
A-1010 Wien
E-Mail: bol@adv.magwien.gv.at
------------------------------
Date: 24 Oct 2006 09:43:06 GMT
From: Eric Bohlman <ebohlman@omsdev.com>
Subject: Re: FAQ 4.18 Does Perl have a Year 2000 problem? Is Perl Y2K compliant?
Message-Id: <Xns98662FBFEFE74ebohlmanomsdevcom@130.133.1.4>
PerlFAQ Server <brian@stonehenge.com> wrote in
news:6p6s04-f7t.ln1@blue.stonehenge.com:
> 4.18: Does Perl have a Year 2000 problem? Is Perl Y2K compliant?
Doesn't this one deserve retirement nearly 7 years later?
------------------------------
Date: Tue, 24 Oct 2006 09:30:47 +0200
From: ismael <ismael.pernas.c@gmail.es>
Subject: Re: File and directory permissions
Message-Id: <ehkfcb$epc52@cesio.mundo-r.com>
Sorry if i wasnt very specific.
The problem is that the file dont have any permissions. It's say, nobody can
read, write or execute the file from a cmd or any program. However this
code says that the file is readable and writable. if i put the file as
"read only" the code says that is readable.
I only want to make some checks and if all its ok the execution wiil
continue in the standard way. If a file is readable make X else make Y. If
a directory is writable make X else make Y. Something like that.
Thanks you. I wish i be specific :)
Best regards
Paul Lalli wrote:
> ismael wrote:
>> I have some problems to get the the permissions on windows with Perl
>> code. I use a simple code that run perfectly in UNIX but give me wrong
>> information on Windows. This is the code:
>>
>> $file = "/home/ismael/pruebaperl/fichero.txt";
>> print "Starting to analize $file\n";
>> if (-e $file){
>> print "found\n";
>> }
>> else {
>> print "not found\n";
>> }
>> if (-x $file){
>> print "executable\n";
>> }
>> if (-r $file){
>> print "readable\n";
>> }
>> if (-w $file){
>> print "writable\n";
>> }
>> print "finished\n";
>>
>> This code allways say that file is readable and writable except if is a
>> read only file.
>> is there a solution for this?
>
> I don't know what the problem to which you're looking for a solution
> is. The above file is reported as readable and writeable. Is that not
> correct? And you said if it's a read-only file, it's not reported as
> readable and writeable? What is it reported as?
>
>> , one library or code? Anything that i do wrong?
>
> Well, primarily what you've done wrong is not told us what the actual
> problem is. What results are you *expecting*, and what results do you
> see? Be very specific.
>
> Paul Lalli
------------------------------
Date: 24 Oct 2006 08:02:21 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: I have no problems eating cereal...after it softens. Why is replacing a simple string so hard then?
Message-Id: <453dc88d$0$1394$da0feed9@news.zen.co.uk>
On 17 Oct 2006 16:48:18 -0700, Brian Wilkins <bwilkins@gmail.com> wrote:
>
>
> samiam@mytrashmail.com wrote:
> [snipped]
>
> Why don't you read in the web page into a scalar variable and chomp all
> the \n characters. Then you have a large scalar variable all on one
> line. Like so (caution not tested):
>
> ====
>
> use strict;
> use warnings;
> use HTML::TokeParser;
>
> $data_file="webpage.htm";
That doesn't compile. You "use strict" but then you don't
declare your variables
my $data_file = "webpage.htm"
> open(DAT, $data_file) || die("Could not open file!");
The error message would be more informative if it included $!
Also, it is generally better to use lexical file handles and the
3-argument form of open:
open my $dat, '<', $data_file
or die "Couldn't open '$data_file' because: $!"
>
> @raw_data=<DAT>;
my @raw_data = <$dat>;
>
> close(DAT);
>
> foreach $line (@raw_data)
missing "my". And I find "for" easier on the eye than "foreach". YMMV
for my $line (@raw_data)
> {
> chomp($line);
> $rawHTML .= $line;
> }
Why are you removing all the line-end characters from the data?
That will break HTML files that have <PRE></PRE> sections, at least.
All the code above would be better written as:
open my $dat, '<', $data_file
or die "Couldn't open '$data_file' because: $!"
my $rawHTML = do { local $/; <$dat> };
close $dat;
Or, better still:
use File::Slurp;
my $rawHTML = read_file( $data_file );
>
> $rawHTML =~ s#<form .*?</form>#BLOCK#sg;
As others have mentioned, a regex is a poor way to parse HTML.
> open(OUTFILE, ">parsed_file.htm");
open my $outfile, '>', "parsed_file.htm"
or die "Can't write to parsed_file.htm because: $!";
>
> print OUTFILE $rawHTML;
>
> close(OUTFILE);
If you used File::Slurp, then replace the above with:
write_file( 'parsed_file.htm' );
> You can also use HTML::TokeParser. It may work better in this case.
It work work better than a plain s/// for most HTML.
------------------------------
Date: 24 Oct 2006 07:10:21 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <453dbc5d$0$81355$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: Tue, 24 Oct 2006 10:55:25 +0100
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: question about using jpegtran for lossless compression of jpegs
Message-Id: <453de30d$0$8741$ed2619ec@ptn-nntp-reader02.plus.net>
ewaguespack@gmail.com wrote:
>
> well I am not an expert at jpeg file structure, but if you download
> that jstrip program and enable the optional "jfif header removal" your
> get a 18 byte (i believe) reduction in size beyond what jpegtran
> provided.
>
Apologies - I was reading "EXIF" and/or IPTC
for jfif.
(btw, jfif isn't technically a header, but comments
in the JPEG stream, but I'm guessing you already knew that)
BugBear
------------------------------
Date: 24 Oct 2006 11:07:06 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Scripting an EXE
Message-Id: <omlrj2poeu0hj4q4rfj0o6fuo5n6sr744u@4ax.com>
On 23 Oct 2006 20:43:13 -0700, "JKG" <JKGambhir@gmail.com> wrote:
>C:\>(echo 2; echo q) | t2t2
>
>Though that is all I want, I will still do it with a program (perl
>script program) and try to take the log of the output.
Well then you have to use Perl's "equivalent" of echo, which happens
to be print(). Read more about it at
perldoc -f print
As far as the "take the log of the output" goes, one would need to
understand what you really mean. If t2t2 logs into a file, the you can
subsequently open() it for reading. If it prints to STDOUT, then
you're in a situation in which you want both to send something into a
program's STDIN and read from its STDOUT, in which case there's a
module especially designed to handle it, which happens to be
IPC::Open2.
HTH,
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 24 Oct 2006 11:13:01 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: string substitution for a file, without replacing partial string?
Message-Id: <k0mrj2d8iu460sok7fldlr542pe0qq8148@4ax.com>
On Mon, 23 Oct 2006 21:32:19 GMT, "Arved Sandstrom"
<asandstrom@accesswave.ca> wrote:
>Come, come, that's the standard initial reply from a disgruntled consumer.
>Have you never worked tech support for a software product? :-)
HAve you ever seen gavino's previous "work"?
http://groups.google.it/group/comp.lang.perl.misc/search?group=comp.lang.perl.misc&q=gavino
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 24 Oct 2006 11:14:39 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Why I no longer use Perl
Message-Id: <u9mrj2tjd43crh49erhfp7ush5b8sduar0@4ax.com>
On Mon, 23 Oct 2006 21:57:48 +0200, "Peter J. Holzer"
<hjp-usenet2@hjp.at> wrote:
>You don't include enough information about your environment to be sure
>where the bug is, but it is probably in perl 5.8.0 and was later fixed.
>There were quite a few unicode-related bugs in 5.8.0. However, perl
>5.8.0 is now more than 4 years old and was superceded by perl 5.8.1 more
>than three years ago.
However AIUI the point is that for some reason the OP seems to find
5.8.0's buggy behaviour to be the "right" one...
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
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 9884
***************************************
