[28899] in Perl-Users-Digest
Perl-Users Digest, Issue: 143 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Feb 16 06:10:14 2007
Date: Fri, 16 Feb 2007 03:09:07 -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, 16 Feb 2007 Volume: 11 Number: 143
Today's topics:
Re: Geting Windows NT services and drives. <findingAri@gmail.com>
Re: how to install/use MP3::Tag in Windows environment? ethopandit@gmail.com
New to Perl, OOP inheritance <petermichaux@gmail.com>
Re: New to Perl, OOP inheritance anno4000@radom.zrz.tu-berlin.de
Re: obfuscated <jurgenex@hotmail.com>
Re: obfuscated <mark.clementsREMOVETHIS@wanadoo.fr>
Re: pattern serach over many files <tadmc@augustmail.com>
Re: pattern serach over many files <wahab-mail@gmx.de>
Re: pattern serach over many files <wahab-mail@gmx.de>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
problem reading remote file. <nitte.sudhir@gmail.com>
Re: problem reading remote file. <wahab-mail@gmx.de>
Re: Regexp for email addresses. <ddunham@redwood.taos.com>
Re: Regexp for email addresses. <abigail@abigail.be>
set a variable with a specified element of an array... <gniagnia@gmail.com>
Re: set a variable with a specified element of an arra anno4000@radom.zrz.tu-berlin.de
Re: set a variable with a specified element of an arra <wahab-mail@gmx.de>
Re: set a variable with a specified element of an array <gniagnia@gmail.com>
Why can't I access variable from other subroutine? <itfred@cdw.com>
Re: Why can't I access variable from other subroutine? <jurgenex@hotmail.com>
Re: Why can't I access variable from other subroutine? anno4000@radom.zrz.tu-berlin.de
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 16 Feb 2007 00:08:09 -0800
From: "490" <findingAri@gmail.com>
Subject: Re: Geting Windows NT services and drives.
Message-Id: <1171613288.950978.200020@j27g2000cwj.googlegroups.com>
On Feb 15, 8:32 pm, Christian Winter <thepoet_nos...@arcor.de> wrote:
> 490 wrote:
> > I am trying to get win NT services and drives detailes.
> > I used the code:
>
> > 'WINMSD /f' ;
> > 'set >info.txt';
>
> > And then i go through the details and get what i want form the txt
> > file.
> > The problem is that this is a very ugly way and it uses alot of CPU &
> > Memory Usage.
>
> > Does any body have a better and faster way?!
>
> I'd use Win32::OLE and the WMI for that. The WMI classes are
> well documented over at msdn.microsoft.com (there you will find
> all attributes explained, like e.g. the DriveType numbers I'm
> using in the example), and using them is quite straight forward.
>
> Though if I recall correctly, WMI has to be installed manually
> on NT 4 (requiring SP4 or above), but this has the bonus of
> running on later MS-OSes without changes, whereas the "write
> text" option of winmsd got lost somewhere along the way.
>
> ----------------------------------------------------------------
> #!/perl
>
> use strict;
> use warnings;
> use Win32::OLE qw(in);
>
> my $computer = "."; # MS's short notation for "this host"
>
> my $wmi = Win32::OLE->GetObject(
> 'winmgmts:{impersonationLevel=impersonate,(security)}//' .
> $computer .
> '/root/CIMV2'
> );
>
> print "Logical Drives:" . $/;
> print "===============" . $/;
>
> my $drives = $wmi->ExecQuery(
> 'SELECT * FROM Win32_LogicalDisk ' .
> 'WHERE DriveType = 2 OR DriveType = 3'
> );
>
> foreach my $drive ( in($drives) )
> {
> printf( "%s %-12s Bytes, %-12s Bytes free$/",
> $drive->{'Name'},
> $drive->{'Size'},
> $drive->{'FreeSpace'}
> );
>
> }
>
> print "Services:" . $/;
> print "=========" . $/;
>
> my $services = $wmi->ExecQuery('SELECT * FROM Win32_Service');
>
> foreach my $srvc ( in($services) )
> {
> printf("%-30s %10s: %-10s (%s)$/",
> $srvc->{'Name'},
> "[" . $srvc->{'StartMode'} . "]",
> $srvc->{'State'},
> $srvc->{'PathName'}
> );}
>
> ----------------------------------------------------------------
>
> HTH
> -Chris
I thought about that but it steel uses lots of CPU.
Isn't there a perl module way?
------------------------------
Date: 15 Feb 2007 17:54:31 -0800
From: ethopandit@gmail.com
Subject: Re: how to install/use MP3::Tag in Windows environment?
Message-Id: <1171590871.489445.206180@h3g2000cwc.googlegroups.com>
On Feb 6, 3:57 pm, "Ozmodiar" <Ozmod...@springBOBBITTlake.net> wrote:
> ahoy:
>
> i am working on a project in Windows XP where i must read MP3 file ID3v2
> information (particularly long (>30 char) Artist and Title)
>
> (This is perl, v5.8.0 built for MSWin32-x86-multi-thread)
>
> i was able to install and use MP3::Info, by downloading the source to
> mp3-info.ppm and doing
> C:\Perl> ppm install mp3-info
>
> i could access this from my perl code and it seemed to work as advertised,
> but this module does not let me get at the long artist/title information.
>
> it looks like the module i really want is MP3::Taghttp://search.cpan.org/~ilyaz/MP3-Tag-0.9709/Tag.pm
>
> i'm not a windows/perl heavy and don't understand how to go from the
> downloadable
> modules/MP3-Tag-0.9709.tar.gz
> file, to getting this installed from DOS command prompt (C:\Perl>)
>
> i used Stuffit to extract the contents into my Perl dir
> then did
> C:\Perl> perl Makefile.pl
> (got back:
> Writing Makefile for MP3::Tag
> Writing Makefile for MP3::Tag
> )
>
> then i did
> C:\Perl> ppm install Tag
> (got back:
> Error: 'Tag' not found. Please 'search' for it first.
> )
>
> Tag.pm is in my working dir, as are folders: /examples, /Tag, /tk-tag
> don't know why "not found" (or what i'm really doing).
>
> can anyone baby-talk me through this?
>
> thanks very much,
> -rr
Run ppm install MP3::Tag
------------------------------
Date: 15 Feb 2007 22:20:45 -0800
From: "Peter Michaux" <petermichaux@gmail.com>
Subject: New to Perl, OOP inheritance
Message-Id: <1171606845.525442.74290@v33g2000cwv.googlegroups.com>
Hi,
I'm new to Perl (from C, JavaScript, Ruby) and going through the Camel
book.
Below is my an example of trying to write Ruby/Java style class-based
inheritance in Perl. (In JavaScript, Ruby and Java I would write like
this <URL: http://peter.michaux.ca/article/1>) The first eight lines
of each new subroutine below seems quite clunky. I'm trying to make it
so the new can be called either to instantiate a new object or be
called as super from a child class's constructor. I only want to name
the parent class once in the @ISA and use SUPER everywhere else so I
can change the inheritance chain easily.
package Person;
sub new {
my $invocant = shift;
my $this;
if (ref($invocant)) {
$this = $invocant;
} else {
$this = {};
bless($this, $invocant);
}
my ($name) = @_;
$this->{name} = $name;
return $this;
}
sub toString {
$this = shift;
return $this->{name};
}
# ---------------------------------------------
package Employee;
our @ISA = ('Person');
sub new {
my $invocant = shift;
my $this;
if (ref($invocant)) {
$this = $invocant;
} else {
$this = {};
bless($this, $invocant);
}
my ($name, $id) = @_;
$this->SUPER::new($name);
$this->{id} = $id;
return $this;
}
sub toString {
my $this = shift;
return $this->SUPER::toString() . ': ' . $this->{id};
}
# ---------------------------------------------
$ted = Employee->new('Ted', 10);
print ($ted->toString(), "\n");
Any suggestions to clean up the clunky parts of the new subroutines? I
expect that some will say "this is not how you do OOP Inheritance in
Perl." Other options?
Thank you,
Peter
http://peter.michaux.ca
http://forkjavascript.org
------------------------------
Date: 16 Feb 2007 09:06:06 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: New to Perl, OOP inheritance
Message-Id: <53lafuF1tb0v5U2@mid.dfncis.de>
Peter Michaux <petermichaux@gmail.com> wrote in comp.lang.perl.misc:
> Hi,
>
> I'm new to Perl (from C, JavaScript, Ruby) and going through the Camel
> book.
>
> Below is my an example of trying to write Ruby/Java style class-based
> inheritance in Perl. (In JavaScript, Ruby and Java I would write like
> this <URL: http://peter.michaux.ca/article/1>) The first eight lines
> of each new subroutine below seems quite clunky. I'm trying to make it
> so the new can be called either to instantiate a new object or be
> called as super from a child class's constructor. I only want to name
> the parent class once in the @ISA and use SUPER everywhere else so I
> can change the inheritance chain easily.
So if ->new is called as an object method it (re-)initializes the
object. That's a reasonable approach, though it might be clearer
to have separate methods (object method ->init, class method ->new)
for that.
> package Person;
>
> sub new {
> my $invocant = shift;
> my $this;
> if (ref($invocant)) {
> $this = $invocant;
> } else {
> $this = {};
> bless($this, $invocant);
> }
> my ($name) = @_;
> $this->{name} = $name;
> return $this;
> }
>
> sub toString {
> $this = shift;
> return $this->{name};
> }
>
> # ---------------------------------------------
>
> package Employee;
> our @ISA = ('Person');
>
> sub new {
> my $invocant = shift;
> my $this;
> if (ref($invocant)) {
> $this = $invocant;
> } else {
> $this = {};
> bless($this, $invocant);
> }
> my ($name, $id) = @_;
>
> $this->SUPER::new($name);
> $this->{id} = $id;
> return $this;
> }
>
> sub toString {
> my $this = shift;
> return $this->SUPER::toString() . ': ' . $this->{id};
> }
>
> # ---------------------------------------------
>
> $ted = Employee->new('Ted', 10);
> print ($ted->toString(), "\n");
>
>
> Any suggestions to clean up the clunky parts of the new subroutines? I
> expect that some will say "this is not how you do OOP Inheritance in
> Perl." Other options?
You can pack most of the "clunky part" in one statement:
sub new {
my $invocant = shift;
my $this = ref( $invocant) ? $invocant : bless {}, $invocant;
my ($name) = @_;
# ...
}
Anno
------------------------------
Date: Fri, 16 Feb 2007 01:20:34 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: obfuscated
Message-Id: <CF7Bh.2817$Zp3.2116@trndny04>
john.swilting wrote:
> john.swilting wrote:
>
>> john.swilting wrote:
>>
>>> john.swilting wrote:
>>>
>>>>> perl -el { { slurp(<$lwp = HTTP::Request->new(GET=>
>>>>> 'file:/etc/passwd');;>
>>>> print $_);redo;};};
>>> :-[
>> it is very small I do not have tries to make it go but when think
> I have to test it does not walk but in 2000 it is odd Perl of the
> times
WTFH are you talking about? Your text doesn't make any sense, it doesn't
even form a valid English sentence.
Is this some kind of filler text to get around spam detection software?
jue
------------------------------
Date: Fri, 16 Feb 2007 07:36:09 +0100
From: Mark Clements <mark.clementsREMOVETHIS@wanadoo.fr>
Subject: Re: obfuscated
Message-Id: <45d550d9$0$27370$ba4acef3@news.orange.fr>
Jürgen Exner wrote:
> john.swilting wrote:
>> john.swilting wrote:
>>
>>> john.swilting wrote:
>>>
>>>> john.swilting wrote:
>>>>
>>>>>> perl -el { { slurp(<$lwp = HTTP::Request->new(GET=>
>>>>>> 'file:/etc/passwd');;>
>>>>> print $_);redo;};};
>>>> :-[
>>> it is very small I do not have tries to make it go but when think
>> I have to test it does not walk but in 2000 it is odd Perl of the
>> times
>
> WTFH are you talking about? Your text doesn't make any sense, it doesn't
> even form a valid English sentence.
> Is this some kind of filler text to get around spam detection software?
>
He's finding it increasingly hard to get decent responses on
fr.comp.lang.perl: every so often he announces (loosely translated) that
he's not going to post anymore on the French newsgroup because it
doesn't get any traffic and the "us" one is much better, and then he
continues to post there and ask questions.... If it's any consolation
his French grammar isn't exactly perfect either. That being said,
neither is mine :)
Mark
------------------------------
Date: Thu, 15 Feb 2007 20:53:04 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: pattern serach over many files
Message-Id: <slrneta74g.ose.tadmc@tadmc30.august.net>
pavan734@gmail.com <pavan734@gmail.com> wrote:
> On Feb 15, 4:53 pm, Tad McClellan <t...@augustmail.com> wrote:
>> pavan...@gmail.com <pavan...@gmail.com> wrote:
>> > Hi,
>> > Suppose I have got 3 files like this
>>
>> > file1.txt file2.txt file3.txt
>> > abc gsywg wrtw
>> > def abc abc hshs dhwu wwg
>> > dadq aft hhs gtc ffs
>> > abc ttsg abc hhshh abc
>> my @file1 = ('abc', 'def abc', 'dadq aft', 'abc ttsg');
>> my @file2 = ('gsywg', 'abc hshs', 'hhs gtc', 'abc hhshh');
>> my @file3 = ('wrtw', 'dhwu wwg', 'ffs', 'abc');
> I think you have misunderstood.
No, I think I didn't.
> file1 name is file1.txt and `abc',
> 'def abc', 'dadq aft', `abc ttsg' are its contents.
Yes, I understood all of that, but I didn't want to litter my
filesystem with a bunch of files just for testing.
I left it to you to figure out yourself how to read each of
the 3 files into an array, or to adapt it to read 3 files
in parallel.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 16 Feb 2007 09:28:44 +0100
From: Mirco Wahab <wahab-mail@gmx.de>
Subject: Re: pattern serach over many files
Message-Id: <er3qa0$he8$1@mlucom4.urz.uni-halle.de>
Tad McClellan wrote:
> pavan734@gmail.com <pavan734@gmail.com> wrote:
>> I think you have misunderstood.
>
> No, I think I didn't.
>
>> file1 name is file1.txt and `abc',
>> 'def abc', 'dadq aft', `abc ttsg' are its contents.
>
> Yes, I understood all of that, but I didn't want to litter my
> filesystem with a bunch of files just for testing.
>
> I left it to you to figure out yourself how to read each of
> the 3 files into an array, or to adapt it to read 3 files
> in parallel.
I know you wouldn't hesitate to spell out
a complete solution for al this within 45
seconds if necessary, but I believe in this
case your example wasn't really a good one.
I actually tried to start from it and pull
a solution but there are (imho) some larger
difficulties from a beginners view because
you can't really index file lines via
loop variables.
The closest working solution to that (without
cluttering the file system) I found was this:
#!/usr/bin/perl
use warnings;
use strict;
my $file1 = join "\n", ('abc', 'def abc', 'dadq aft', 'abc ttsg');
my $file2 = join "\n", ('gsywg', 'abc hshs', 'hhs gtc', 'abc hhshh');
my $file3 = join "\n", ('wrtw', 'dhwu wwg', 'ffs', 'abc');
open my $h1, '<', \$file1 or warn "$!";
open my $h2, '<', \$file2 or warn "$!";;
open my $h3, '<', \$file3 or warn "$!";;
my $cnt=0;
foreach my $i ( 1 .. 3 ) {
$cnt += ( (<$h1> =~ /abc/)
+ (<$h2> =~ /abc/)
+ (<$h3> =~ /abc/) )
== 0 ? 1 : 0;
}
print int($cnt),"\n";
As you can see, to adopt to a 'file reading solution',
you have to completely rewrite the loop ... ;-)
(If I'm not completely mistaken)
Regards
Mirco (intermediate level)
------------------------------
Date: Fri, 16 Feb 2007 09:33:47 +0100
From: Mirco Wahab <wahab-mail@gmx.de>
Subject: Re: pattern serach over many files
Message-Id: <er3sfi$hp6$2@mlucom4.urz.uni-halle.de>
Tad McClellan wrote:
> pavan734@gmail.com <pavan734@gmail.com> wrote:
>> I think you have misunderstood.
> No, I think I didn't.
>> file1 name is file1.txt and `abc',
>> 'def abc', 'dadq aft', `abc ttsg' are its contents.
> Yes, I understood all of that, but I didn't want to litter my
> filesystem with a bunch of files just for testing.
> I left it to you to figure out yourself how to read each of
> the 3 files into an array, or to adapt it to read 3 files
> in parallel.
I know you wouldn't hesitate to spell out
a complete solution for all this within 45
seconds if necessary, but I believe in this
case your example wasn't really a good one.
I actually tried to start from it and pull
a solution but there are (imho) some larger
difficulties from a beginners view because
you can't really index file lines via
loop variables.
The closest working solution to that (without
cluttering the file system) I found was this:
#!/usr/bin/perl
use warnings;
use strict;
my $file1 = join "\n", ('abc', 'def abc', 'dadq aft', 'abc ttsg');
my $file2 = join "\n", ('gsywg', 'abc hshs', 'hhs gtc', 'abc hhshh');
my $file3 = join "\n", ('wrtw', 'dhwu wwg', 'ffs', 'abc');
open my $h1, '<', \$file1 or warn "$!";
open my $h2, '<', \$file2 or warn "$!";;
open my $h3, '<', \$file3 or warn "$!";;
my $cnt=0;
my $line=0;
while( ++$line ) {
last if( eof($h1) || eof($h2) || eof($h3) );
++$cnt unless ( (<$h1> =~ /abc/)
+ (<$h2> =~ /abc/)
+ (<$h3> =~ /abc/) )
}
print $cnt,"\n";
As one can see, to adopt to a 'file reading solution',
you have to completely rewrite the loop ... ;-)
(If I'm not completely mistaken)
Regards
Mirco (intermediate level)
------------------------------
Date: 16 Feb 2007 08:10:14 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <45d566e5$0$3157$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: 16 Feb 2007 01:45:50 -0800
From: "kath" <nitte.sudhir@gmail.com>
Subject: problem reading remote file.
Message-Id: <1171619149.956661.265560@l53g2000cwa.googlegroups.com>
Hello,
I have a script to read remote file. The script goes as follows,
#!C:\Perl\bin\perl.exe
$remote= '\\\remotehost\remotedir\remotefile.jml';
open(fp, $remote) or die ("could not open the file");
print while(<fp>);
close(fp);
This script runs fine on my windows machine. But the same script when
I run in UNIX, after changing the shebang line to /usr/bin/perl, I
get
could not open the file file_name.pl at 4
The remote host from which I am trying to read the file is also
Windows box.
1. where am i making wrong?
2. Why the script is not running on UNIX?
Thank you,
Regards,
kath.
------------------------------
Date: Fri, 16 Feb 2007 11:23:39 +0100
From: Mirco Wahab <wahab-mail@gmx.de>
Subject: Re: problem reading remote file.
Message-Id: <er411q$j9j$1@mlucom4.urz.uni-halle.de>
kath wrote:
> I have a script to read remote file. The script goes as follows,
> #!C:\Perl\bin\perl.exe
> $remote= '\\\remotehost\remotedir\remotefile.jml';
> open(fp, $remote) or die ("could not open the file");
> print while(<fp>);
> close(fp);
> This script runs fine on my windows machine. But the same script when
> I run in UNIX, after changing the shebang line to /usr/bin/perl, I
> get
> could not open the file file_name.pl at 4
>
> The remote host from which I am trying to read the file is also
> Windows box.
> 1. where am i making wrong?
> 2. Why the script is not running on UNIX?
Under Unix, you need to have access to the
windows box by smbclient and fiends.
Your code traanslated to the unix world
could read like the following:
use strict;
use warnings;
# this is what you used to use
my $winrmt = '\\\remotehost\remotedir\remotefile.jml';
# make sure you get the access rights correct,
# maybe you can drop username/password completely
my $unxrmt = '-n --username=kath --password=kath01 smb:/'
. join '/', split /\\+/, $winrmt;
# pull some adrenaline:
print "trying: $unxrmt \n";
my $pid = open HANDLE, "smbget $unxrmt |" or die "fork error: $!";
close HANDLE;
# now your remote file should reside in your current
# directory. Please check out other options if the
# smbclient family e.g.: $> man smbget
If it won't work, check out what $unxrmt looks like
and pot it back here ...
Regards
M.
------------------------------
Date: Fri, 16 Feb 2007 00:15:53 GMT
From: Darren Dunham <ddunham@redwood.taos.com>
Subject: Re: Regexp for email addresses.
Message-Id: <ZI6Bh.45076$Gr2.9896@newssvr21.news.prodigy.net>
cmic <cmic@caramail.com> wrote:
> On 14 fév, 22:55, Abigail <abig...@abigail.be> wrote:
>> use 5.9.5; # In fact, you need the newest blead.
>>
> ...skipped
>> --
>> perl -wlpe '}{$_=$.}{' file # Count the number of lines.
> ^^^^^^^^^^^^^
> As a Perl beginner, i'm a bit surprised to see this working. Could you
> explain why (and how) these "counter-intuitive" } and { works ? And
> how come you found out this trick ? Very very curious about this.
Take a look at the 'perlrun' perldoc for an explanation of the -p flag.
You'll note that code you supply is already within a set of brackets.
Does that make sense?
--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
------------------------------
Date: 16 Feb 2007 08:23:00 GMT
From: Abigail <abigail@abigail.be>
Subject: Re: Regexp for email addresses.
Message-Id: <slrnetaqep.ijp.abigail@alexandra.abigail.be>
cmic (cmic@caramail.com) wrote on MMMMCMXVI September MCMXCIII in
<URL:news:1171579379.110397.135680@v33g2000cwv.googlegroups.com>:
:: Hello
::
:: On 14 fév, 22:55, Abigail <abig...@abigail.be> wrote:
:: > use 5.9.5; # In fact, you need the newest blead.
:: >
:: ...skipped
:: > --
:: > perl -wlpe '}{$_=$.}{' file # Count the number of lines.
:: ^^^^^^^^^^^^^
::
:: As a Perl beginner, i'm a bit surprised to see this working. Could you
:: explain why (and how) these "counter-intuitive" } and { works ? And
See perlrun, or do a google search for it. It has been explained
many times.
:: how come you found out this trick ? Very very curious about this.
A remark Chip Salzenberg once (in the previous century) made in
The Perl Journal.
Abigail
--
perl -wle'print"Êõóô áîïôèåò Ðåòì Èáãëåò"^"\x80"x24'
------------------------------
Date: 16 Feb 2007 00:06:58 -0800
From: "gniagnia" <gniagnia@gmail.com>
Subject: set a variable with a specified element of an array...and all elements that follows
Message-Id: <1171613218.840377.198050@j27g2000cwj.googlegroups.com>
Hi all,
My array @array contains AT LEAST 7 elements.
I would like to set a variable that will contain all elements of this
array beginning from the 7th elements.
Is it easily doable?
thanks in advance.
------------------------------
Date: 16 Feb 2007 08:44:25 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: set a variable with a specified element of an array...and all elements that follows
Message-Id: <53l979F1tb0v5U1@mid.dfncis.de>
gniagnia <gniagnia@gmail.com> wrote in comp.lang.perl.misc:
> Hi all,
>
>
> My array @array contains AT LEAST 7 elements.
> I would like to set a variable that will contain all elements of this
> array beginning from the 7th elements.
>
> Is it easily doable?
Sure, that's an array slice (see perldata).
my @tail = @array[ 6 .. $#array]
Anno
------------------------------
Date: Fri, 16 Feb 2007 09:41:41 +0100
From: Mirco Wahab <wahab-mail@gmx.de>
Subject: Re: set a variable with a specified element of an array...and all elements that follows
Message-Id: <er3r29$hjn$1@mlucom4.urz.uni-halle.de>
gniagnia wrote:
> My array @array contains AT LEAST 7 elements.
> I would like to set a variable that will contain all elements of this
> array beginning from the 7th elements.
>
> Is it easily doable?
...
my @array = qw' 1 2 3 4 5 6 7 8 9 10 '; # qn{ .. } is missing :-/
my $index = 7;
# just copy elements above (non destructive)
my @over7n = @array[$index-1 .. @array-1];
# concatenate elements into string
my $over7s = join ',', @array[$index-1 .. @array-1];
# remove these elements from source array (destructive)
my @over7d = splice @array, $index-1;
...
please look up:
array slice
splice
Regards
Mirco
------------------------------
Date: 16 Feb 2007 01:03:58 -0800
From: "gniagnia" <gniagnia@gmail.com>
Subject: Re: set a variable with a specified element of an array...and all elements that follows
Message-Id: <1171616638.623263.101430@q2g2000cwa.googlegroups.com>
On 16 f=E9v, 09:41, Mirco Wahab <wahab-m...@gmx.de> wrote:
> gniagnia wrote:
> > My array @array contains AT LEAST 7 elements.
> > I would like to set a variable that will contain all elements of this
> > array beginning from the 7th elements.
>
> > Is it easily doable?
>
> ...
> my @array =3D qw' 1 2 3 4 5 6 7 8 9 10 '; # qn{ .. } is missing :-/
>
> my $index =3D 7;
>
> # just copy elements above (non destructive)
> my @over7n =3D @array[$index-1 .. @array-1];
>
> # concatenate elements into string
> my $over7s =3D join ',', @array[$index-1 .. @array-1];
>
> # remove these elements from source array (destructive)
> my @over7d =3D splice @array, $index-1;
> ...
>
> please look up:
>
> array slice
> splice
>
> Regards
>
> Mirco
It's working!
Thanks a lot for your help.
------------------------------
Date: Thu, 15 Feb 2007 23:07:40 -0500
From: Fred <itfred@cdw.com>
Subject: Why can't I access variable from other subroutine?
Message-Id: <DbGdnUWsuf6Qs0jYnZ2dnUVZ_syunZ2d@comcast.com>
The two subs below are in a package named Mypkg.pm.
The LoadConfig sub uses AppConfig. In this sub I
can print the host variable using $config->host().
So I added the line our $hostx = $config->host(),
to assign this to $hostx. Now in the TestSub sub,
I try and print Mypkg::LoadConfig::hostx, but it
never prints. How can I access hostx from the
TestSub subroutine?
-Thanks
sub LoadConfig
{
shift @_;
my ($cfgfile, $prn) = @_;
my $config = '';
$config = AppConfig->new(
{
CASE => 1,
PEDANTIC => 0,
CREATE => 1,
ERROR => sub {},
GLOBAL => { ARGCOUNT => ARGCOUNT_ONE }
}
);
$config->file($cfgfile);
####### Can't access this below in DBConnect ########
our $hostx = $config->host();
if ($prn eq 'p') {
print "Configuration file: $cfgfile\n";
print "dbname:\t\t".$config->dbname()."\n";
print "host:\t\t".$config->host()."\n";
print "port:\t\t".$config->port()."\n";
print "username:\t".$config->username()."\n";
}
}
sub TestSub
{
LoadConfig('/etc/my.conf');
######## Cannot print host variable from LoadConfig above ########
print Mypkg::LoadConfig::hostx;
}
------------------------------
Date: Fri, 16 Feb 2007 05:40:30 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Why can't I access variable from other subroutine?
Message-Id: <itbBh.6601$2%1.4893@trndny02>
Fred wrote:
> The two subs below are in a package named Mypkg.pm.
> The LoadConfig sub uses AppConfig. In this sub I
> can print the host variable using $config->host().
> So I added the line our $hostx = $config->host(),
> to assign this to $hostx. >
> sub LoadConfig
[...]
> our $hostx = $config->host();
The "our" makes this a variable that is visible only within the sub
LoadConfig()
[...]
> }
>
>
> sub TestSub
> {
> LoadConfig('/etc/my.conf');
>
> ######## Cannot print host variable from LoadConfig above ########
> print Mypkg::LoadConfig::hostx;
>
> }
> Now in the TestSub sub,
> I try and print Mypkg::LoadConfig::hostx, but it
> never prints. How can I access hostx from the
> TestSub subroutine?
Technically correct but from a software engineering point of view rather
ugly: Make $hostx a global variable.
Better: have LoadConfig() return() the value of $hostx to the caller.
jue
------------------------------
Date: 16 Feb 2007 11:03:42 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Why can't I access variable from other subroutine?
Message-Id: <53lhceF1n32jvU1@mid.dfncis.de>
Fred <itfred@cdw.com> wrote in comp.lang.perl.misc:
> The two subs below are in a package named Mypkg.pm.
> The LoadConfig sub uses AppConfig. In this sub I
> can print the host variable using $config->host().
> So I added the line our $hostx = $config->host(),
> to assign this to $hostx. Now in the TestSub sub,
> I try and print Mypkg::LoadConfig::hostx, but it
> never prints. How can I access hostx from the
> TestSub subroutine?
>
> -Thanks
You don't show the package line that precedes this. I'll
assume it's
package Mypkg::LoadConfig;
[snip]
> ####### Can't access this below in DBConnect ########
> our $hostx = $config->host();
[snap]
> ######## Cannot print host variable from LoadConfig above ########
> print Mypkg::LoadConfig::hostx;
Scalar variables have a "$" in front of them. Try
print "$Mypkg::LoadConfig::hostx\n";
Anno
------------------------------
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 V11 Issue 143
**************************************
