[24361] in Perl-Users-Digest
Perl-Users Digest, Issue: 6550 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue May 11 06:05:54 2004
Date: Tue, 11 May 2004 03:05:08 -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, 11 May 2004 Volume: 10 Number: 6550
Today's topics:
Re: Conditional Statement failure --- if ($a>0) <bernard.el-haginDODGE_THIS@lido-tech.net>
Re: Confused Newbie question: Decimal to IP <krahnj@acm.org>
Re: Confused Newbie question: Decimal to IP (Anno Siegel)
Font Embedding in PDF (Aqua)
IPC::Shareable and threads <nospam@gobotherverisign.com>
Need example of module+cgi+data distribution <nomail.please@no.mail.com>
Re: Need example of module+cgi+data distribution <odyniec-usenet@odyniec.net>
Re: Permission denied with PERL/APACHE <tadmc@augustmail.com>
Re: Permission denied with PERL/APACHE (Walter Roberson)
Re: Permission denied with PERL/APACHE <gnari@simnet.is>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Printing Array's content with carriage return (\n) <lv@aol.com>
Re: Set Permanent ENV variables on Windows (Prabh)
Re: Set Permanent ENV variables on Windows <1usa@llenroc.ude>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 11 May 2004 08:05:55 +0200
From: "Bernard El-Hagin" <bernard.el-haginDODGE_THIS@lido-tech.net>
Subject: Re: Conditional Statement failure --- if ($a>0)
Message-Id: <Xns94E6526AED619elhber1lidotechnet@62.89.127.66>
Ala Qumsieh <xxala_qumsiehxx@xxyahooxx.com> wrote:
> Bernard El-Hagin wrote:
>> Web Surfer <raisin@delete-this-trash.mts.net> wrote:
>>
>> [...]
>>
>>
>>
>>>To count the number of elements in an array you might want to
>>>consider doing the following :
>>>
>>>$count = scalar @array;
>>
>>
>>
>> To count the number of elements in an array *you* might want to
>> consider doing the following:
>>
>>
>> $count = @array;
>
> Nothing wrong with using scalar() explicitly.
Where did I say there was something wrong with using scalar()
explicitly? "[...] might want to consider [...]"
> Personally, I don't, but some people find that clearer. I would
> *encourage* anybody to use it if it helps their maintainability.
Shirley.
--
Cheers,
Bernard
------------------------------
Date: Mon, 10 May 2004 23:17:11 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: Confused Newbie question: Decimal to IP
Message-Id: <40A00D72.D0D4CE4E@acm.org>
Monica Roman wrote:
>
> I've read a lot of the threads on this conversion but could not figure
> out which one is the correct function.
>
> I have never written PERL before, but I want to give it a try and be
> able to convert decimal numbers into IP addresses in the PERL script
> used to load the IPs plus other data into an Oracle database. Right
> now I use a SQL function within Oracle, but it slows down everything!
>
> Can someone help the translate into PERL the following SQL function?
>
> create or replace function int2ip(ip int)
> return varchar2
> is
> ip_address varchar2(15);
> t number;
> w int(3);
> x int(3);
> y int(3);
> z int(3);
>
> begin
>
> t:= ip / 256;
> w:= 256 * (t - FLOOR(t));
> t:= (FLOOR (t))/ 256;
> x:= 256 * (t - FLOOR(t));
> t:= (FLOOR (t)) / 256;
> y:= 256 * (t - FLOOR(t));
> z:= FLOOR (t);
>
> ip_address := z||'.'||y||'.'||x||'.'||w;
>
> return ip_address;
> end int2ip;
A direct Perl translation would be something like:
use POSIX qw( floor );
sub int2ip {
my $ip = shift;
my $t = $ip / 256;
my $w = 256 * ( $t - floor $t );
$t = floor( $t ) / 256;
my $x = 256 * ( $t - floor $t );
$t = floor( $t ) / 256;
my $y = 256 * ( $t - floor $t );
my $z = floor $t;
return "$z.$y.$x.$w";
}
However that is still relatively slow. A more Perlish solution would
be:
sub int2ip { join '.', unpack 'CCCC', pack 'N', $_[ 0 ] }
Which is a lot faster. But an even faster solution would be:
use Socket;
sub int2ip { inet_ntoa inet_aton $_[ 0 ] }
John
--
use Perl;
program
fulfillment
------------------------------
Date: 11 May 2004 09:47:57 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Confused Newbie question: Decimal to IP
Message-Id: <c7q7gd$a3j$1@mamenchi.zrz.TU-Berlin.DE>
John W. Krahn <krahnj@acm.org> wrote in comp.lang.perl.misc:
> Monica Roman wrote:
[...]
> > Can someone help the translate into PERL the following SQL function?
> >
> > create or replace function int2ip(ip int)
> > return varchar2
> > is
> > ip_address varchar2(15);
> > t number;
> > w int(3);
> > x int(3);
> > y int(3);
> > z int(3);
> >
> > begin
> >
> > t:= ip / 256;
> > w:= 256 * (t - FLOOR(t));
> > t:= (FLOOR (t))/ 256;
> > x:= 256 * (t - FLOOR(t));
> > t:= (FLOOR (t)) / 256;
> > y:= 256 * (t - FLOOR(t));
> > z:= FLOOR (t);
> >
> > ip_address := z||'.'||y||'.'||x||'.'||w;
> >
> > return ip_address;
> > end int2ip;
>
> A direct Perl translation would be something like:
>
> use POSIX qw( floor );
>
> sub int2ip {
> my $ip = shift;
>
> my $t = $ip / 256;
> my $w = 256 * ( $t - floor $t );
> $t = floor( $t ) / 256;
> my $x = 256 * ( $t - floor $t );
> $t = floor( $t ) / 256;
> my $y = 256 * ( $t - floor $t );
> my $z = floor $t;
>
> return "$z.$y.$x.$w";
> }
[snip other solutions]
That can be Perlified a bit (no critique, the OP asked for a direct
translation):
sub int2ip {
my $ip = shift;
$ip *= 256;
join '.', reverse map $_ % 256, map $ip = floor( $ip/256), 1 .. 4;
}
I mention this because it shows a particular difficulty. The step
"map $ip = floor( $ip/256), 1 .. 4"
is meant to produce a list of iterative applications of "floor( $ip/26)"
to $ip. So it does, but the list starts with the operation applied
once to $ip while we want the list to start with the original value of
$ip (the operation applied zero times).
In the given case that could be corrected by multiplying $ip with 256
first, but that's not always applicable, ugly and fragile.
Other possibilities are
map { my $sav = $ip; $ip = floor( $ip/256); $sav} 1 .. 4;
or
map ( "$ip", $ip = floor( $ip/256))[ 0], 1 .. 4;
or
( "$ip", map $ip = floor( $ip/256), 2 .. 4);
but I can't say I like either very much. So currently I'd probably
write this
my @coll;
for ( 1 .. 4 ) {
push @coll, $ip;
$ip = floor( $ip/256);
}
but I can't help thinking there must be a nice map solution.
Is there?
Anno
------------------------------
Date: 11 May 2004 01:07:15 -0700
From: junk@dlink.org (Aqua)
Subject: Font Embedding in PDF
Message-Id: <55d7995c.0405110007.64171ffc@posting.google.com>
Group,
I am using PDF::API2 perl module to create and modify few PDF files. I
am adding few strings to the PDF. But when I run through PitStop tool
I am getting font Helvetica not embedded.
How do I embed standard core font like Helvetica in a PDF?
Regards
Dominic
================ Sample ==============
#!/usr/bin/perl
use PDF::API2;
$pdf=PDF::API2->new;
$fn = "Helvetica";
$font=$pdf->corefont($fn,1);
$page = $pdf->page;
$page->mediabox(595,842);
$txt=$page->text;
$txt->translate(100,700);
$txt->font($font, 18);
$txt->lead(18);
$txt->text('Hello World !');
$pdf->saveas("$0.pdf");
$pdf->end();
exit;
__END__
------------------------------
Date: Tue, 11 May 2004 02:53:07 +0200
From: "Pete" <nospam@gobotherverisign.com>
Subject: IPC::Shareable and threads
Message-Id: <kr2dnTwZVexgvj3dRVn-gw@giganews.com>
Hello,
I was wondering if someone could help me out. I have been trying to get
IPC::Shareable (0.60) to work in a threaded environment (Perl 5.8.3). As per
the example, I created a 'server':
==========================
#!/usr/local/perl-threaded/bin/perl
use IPC::Shareable;
use strict;
use threads;
use threads::shared;
my %my_storage : shared;
my %ipc_options = (
create => 'yes',
exclusive => 0,
mode => 0644,
size => 55,
destroy => 'yes',
);
tie %my_storage, 'IPC::Shareable', 'data', {%ipc_options} or die $!;
$my_storage{'time'} = sprintf ("%0*s", 15, time ());
$a = <STDIN>;
exit 0;
==========================
While the 'server' is running and waiting, I start a new login-shell, and
run this program, the 'client':
==========================
#!/usr/local/perl-threaded/bin/perl
use IPC::Shareable;
use strict;
use threads;
use threads::shared;
my %my_storage : shared;
my %ipc_options = (
create => 'yes',
exclusive => 0,
mode => 0644,
size => 55,
destroy => 'yes',
);
tie %my_storage, 'IPC::Shareable', 'data', {%ipc_options} or die $!;
foreach (sort keys %my_storage) {
print "$_, $my_storage{$_}\n";
}
exit 0;
==========================
All of this does what it is supposed to do. But when I try and store shared
memory data within a live ithread (within a real daemon), things go wrong.
For one, setting "$my_storage{'time'}" no longer evals; and reading the data
from the 'client' test program also shows no data was actually stored in
shared memory.
I really suspect this has something to do with the ithreads. Setting "my
%my_storage : shared", for instance, also makes Perl tie %my_storage to an
underlying, hidden thread, if I remember correctly. So, that might have
something to do with it. So, question, does anyone know how to get
IPC::Shareable to work with ithreads?
I appreciate the help,
Pete
------------------------------
Date: Tue, 11 May 2004 01:09:09 +0000 (UTC)
From: Irving Kimura <nomail.please@no.mail.com>
Subject: Need example of module+cgi+data distribution
Message-Id: <c7p93l$5pe$2@reader2.panix.com>
I'm trying to create a distribution featuring
1. a CGI script (Perl)
2. a collection of Perl modules used by the CGI script
3. data files used by the CGI script
I'm having a hard time coaxing MakeMaker to write a reasonable
Makefile for the above distribution. (Specifically, MakeMaker
doesn't seem to be design to install items such as (1) and (3)
above.)
By any chance, does anyone know of a CPAN module that has something
like 1 and 2 above, or 2 and 3? (I don't expect to be so lucky as
to find a CPAN module that has 1, 2, and 3.) It would help to see
how MakeMaker is used for such modules.
Thanks!
Irv
--
NOTE: In my address everything before the period is backwards.
------------------------------
Date: 11 May 2004 10:14:27 +0200
From: Michal Wojciechowski <odyniec-usenet@odyniec.net>
Subject: Re: Need example of module+cgi+data distribution
Message-Id: <87d65b2xek.fsf@odyniec.odyniec.net>
Irving Kimura <nomail.please@no.mail.com> writes:
> I'm trying to create a distribution featuring
>
> 1. a CGI script (Perl)
> 2. a collection of Perl modules used by the CGI script
> 3. data files used by the CGI script
>
> I'm having a hard time coaxing MakeMaker to write a reasonable
> Makefile for the above distribution. (Specifically, MakeMaker
> doesn't seem to be design to install items such as (1) and (3)
> above.)
I've had a similar experience trying to create a MakeMaker script that
installs an utility along with a few data files. After some struggle,
I've come up with a (kind of) satisfactory result.
The code is available at
http://odyniec.net/projects/cdlist/cdlist-0.1.tar.gz. Makefile.PL is
rather simple and you should have no problem understanding what it
does.
Hope that helps (at least a little bit),
--
Michal Wojciechowski : for(<>){/\s/,$l{$m=$`}=$'}$_ : 10 PRINT "Yet another"
odyniec()odyniec;net : =$l{$c},/O\s/?$c=$'-1:y/"//d : 20 PRINT "Perl hacker"
http://odyniec.net : ,/T\s/?print$':0while$c++<$m : 30 GOTO 10
------------------------------
Date: Mon, 10 May 2004 16:59:23 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Permission denied with PERL/APACHE
Message-Id: <slrnc9vupr.2do.tadmc@magna.augustmail.com>
Nicolas D <nico99@netcourrier.com> wrote:
> i think my problem is that i don't know how configure apache
Then you should be asking in a newsgroup that has something
to do with configuring web servers.
comp.lang.perl.misc is not such a newsgroup.
comp.infosystems.www.servers.unix is though.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 10 May 2004 23:46:20 GMT
From: roberson@ibd.nrc-cnrc.gc.ca (Walter Roberson)
Subject: Re: Permission denied with PERL/APACHE
Message-Id: <c7p48c$c68$1@canopus.cc.umanitoba.ca>
In article <7fe6c964.0405101307.4813fbdf@posting.google.com>,
Nicolas D <nico99@netcourrier.com> wrote:
:the perl script is ok when i excecute it in the directory, i can write
:in the file, but when i launch it with apache i obtain "permission
:denied" when the script open the file with write access rights,
Did you follow my advice to check out your $> and to not assume
that you are in any particular directory? Start by fully-qualifying
the path to your commands.txt file rather than assuming that you can
write in the current working directory.
--
Strange but true: there are entire WWW pages devoted to listing
programs designed to obfuscate HTML.
------------------------------
Date: Mon, 10 May 2004 23:09:53 -0000
From: "gnari" <gnari@simnet.is>
Subject: Re: Permission denied with PERL/APACHE
Message-Id: <c7p20u$tfd$1@news.simnet.is>
"Nicolas D" <nico99@netcourrier.com> wrote in message
news:7fe6c964.0405101307.4813fbdf@posting.google.com...
> Tad McClellan <tadmc@augustmail.com> wrote in message
news:<slrnc9tbgm.u7l.tadmc@magna.augustmail.com>...
> > Nicolas D <nico99@netcourrier.com> wrote:
> >
> >
> > > with the line
> > > "open (FICH, '>>commandes.txt') || die " error: :$!";
> > >
> >
> >
> > Your problem is that you do not have the required permissions, what
else?
> >
> > You don't tell us what OS you are using, but if it is a *nix-flavor
> > one, you may need to change the permisssions on the directory that
> > the file is in, rather than the permissions on the file itself...
>
> my OS is mandrake10 with "Apache-AdvancedExtranetServer/2.0.48
> (Mandrake Linux/5mdk) mod_perl/1.99_11 Perl/v5.8.3 Server at 127.0.0.1
> Port 80"
>
> i write
> "User apache
> Group apache" in httpd2.conf,
>
> the perl script is ok when i excecute it in the directory, i can write
> in the file, but when i launch it with apache i obtain "permission
> denied" when the script open the file with write access rights,
> i create a login with apache user and apache group but no results,
> i think my problem is that i don't know how configure apache to have
> write rights....so i download the perl and apache documentation and i
> ll read it.
> Excuse for my english wich is as bad as my perl knowledge.
then make sure to
a) make sure the writing happens in the directory you
think it does, by doing a chdir or changing the open to
my $fullpath='/fullpath/to/dir/commandes.txt';
open (FICH, ">> $fullpath")
|| die " error: could not open '$fullpath' :$!";
b) make sure that said directory is owner and/or writable
by user or group apache
gnari
------------------------------
Date: Tue, 11 May 2004 02:22:51 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <pP6dnUsaBdHW4j3dRVn-gw@august.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Mon, 10 May 2004 19:51:50 -0500
From: l v <lv@aol.com>
Subject: Re: Printing Array's content with carriage return (\n)
Message-Id: <40a023e5_1@corp.newsgroups.com>
Tad McClellan wrote:
> l v <lv@aol.com> wrote:
>
>
>>I usually use with preference on #2:
>>
>>print map {"$_\n"} @myarray;
>>
>>or
>>
>>map {print "$_\n"} @myarray;
>
>
>
> _Why_ do you prefer #2?
>
>
> I think most people would prefer #1 because it says "print bunch 'o stuff"
> while #2 says "bunch 'o stuff print".
>
>
"print bunch 'o stuff" -- I like it!
#2 purely for comprehension by those in my work area which are VERY
inexperienced with Perl. They see the print block and understand what
is to occur.
I've never really studied which is faster, 'print map ...'
or 'map {print ...' or for. I guess I now have something to do tonight
after all.
Len
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----
------------------------------
Date: 10 May 2004 16:30:48 -0700
From: Prab_kar@hotmail.com (Prabh)
Subject: Re: Set Permanent ENV variables on Windows
Message-Id: <e7774537.0405101530.3218e047@posting.google.com>
"A. Sinan Unur" <1usa@llenroc.ude> wrote in message news:<Xns94E2BC213E7EDasu1cornelledu@132.236.56.8>...
[snipped]
> No it is not. Needs to be done in
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
> \Environment
>
> if you want it system-wide. But, the current user may not have the
> correct rights. Not all of us run XP as Administrators, you know.
>
> I do not know the OP's main purpose. But, if this is an installation
> related issue, then appending to the user's path is appropriate. OTOH,
> this sort of task is probably better handled using one of the free
> installers which would give the user to properly undo the changes made
> during installation.
Thanks a lot everyone for your posts.
I was able to set a system variable from your suggestions.
I was working on two programs, one where it can be safely assumed that
the user has admin rights and can set the System variables. The other
one needs to set the "user" variable.
From the XP, Control panel, System, Advanced, Env variables, I set the
"Foo = Bar" just to see where its put in the registry.
Its placed under [HKEY_USERS\"weird-hexadecimal-number"\Environment].
How can I generate this weird number so that I could programmatically
set the user variable? What local variable got interpolated to
generate this number?
Thanks a lot for your time,
Prabh
------------------------------
Date: 11 May 2004 00:21:52 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude>
Subject: Re: Set Permanent ENV variables on Windows
Message-Id: <Xns94E5CF28E3A1Casu1cornelledu@132.236.56.8>
Prab_kar@hotmail.com (Prabh) wrote in
news:e7774537.0405101530.3218e047@posting.google.com:
> "A. Sinan Unur" <1usa@llenroc.ude> wrote in message
> news:<Xns94E2BC213E7EDasu1cornelledu@132.236.56.8>...
>
> [snipped]
>
>> No it is not. Needs to be done in
>>
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
>> \Environment
>>
>> if you want it system-wide. But, the current user may not have the
>> correct rights. Not all of us run XP as Administrators, you know.
...
> From the XP, Control panel, System, Advanced, Env variables, I set the
> "Foo = Bar" just to see where its put in the registry.
> Its placed under [HKEY_USERS\"weird-hexadecimal-number"\Environment].
>
This is getting way OT here. You are missing the very very obvious:
HKEY_CURRENT_USER\Environment
Sinan.
--
A. Sinan Unur
1usa@llenroc.ude (reverse each component for email address)
------------------------------
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 6550
***************************************
