[24749] in Perl-Users-Digest
Perl-Users Digest, Issue: 6904 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Aug 24 11:06:08 2004
Date: Tue, 24 Aug 2004 08:05:07 -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 Aug 2004 Volume: 10 Number: 6904
Today's topics:
Re: "Perlish Patterns" by Phil Crow <matthew.garrish@sympatico.ca>
Re: convertinga directory path into a hash <zebee@zip.com.au>
Re: convertinga directory path into a hash <tassilo.von.parseval@rwth-aachen.de>
Re: convertinga directory path into a hash <zebee@zip.com.au>
Re: convertinga directory path into a hash <tassilo.von.parseval@rwth-aachen.de>
Re: convertinga directory path into a hash <uri@stemsystems.com>
Exange of informations and objects between PERL and JAV (Lionel)
Information exchange between unrelated processes (pk)
Re: perl interpreter automatically exit windows so how <usenet@morrow.me.uk>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
split question <lepor5e@bestweb.net>
Re: split question <noreply@gunnar.cc>
Re: split question <someone@example.com>
Re: split question <tore@aursand.no>
Re: split question <noreply@gunnar.cc>
Re: split question <rafalk@comcast.net>
Re: split question <uri@stemsystems.com>
Re: split question <mritty@gmail.com>
Re: split question <1usa@llenroc.ude.invalid>
Re: split question <tore@aursand.no>
Using perl and wmi to get MS file version info (kngnsm)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 24 Aug 2004 08:56:03 -0400
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: "Perlish Patterns" by Phil Crow
Message-Id: <zVGWc.12820$_H5.351621@news20.bellglobal.com>
"Peter Michael" <dog@dog.dog> wrote in message
news:cgel3e$pfs1@news-1.bank.dresdner.net...
> Hi,
>
> I ordered "Perlish Patterns" (Apress) by Phil Crow in advance via
> amazon. Now they told me that the book is "no longer available".
> Does anybody know what happened to it?
>
Could be any number of reasons why a book would get cancelled, but often
it's because the publisher doesn't think it will sell (i.e., they try
preselling the book and if they don't get enough orders they don't go to
press with it). If you're really that interested, though, why not try asking
the author directly:
http://www.perl.com/pub/au/Crow_Phil
Matt
------------------------------
Date: Tue, 24 Aug 2004 07:24:43 GMT
From: Zebee Johnstone <zebee@zip.com.au>
Subject: Re: convertinga directory path into a hash
Message-Id: <slrncilqvg.dl1.zebee@zeus.zipworld.com.au>
In comp.lang.perl.misc on Tue, 24 Aug 2004 08:43:56 +0200
Christian Winter <thepoet_nospam@arcor.de> wrote:
> Zebee Johnstone schrieb:
>> I have a unix directory path, say /home/user/mail
>>
>> Not knowing how long it will be, that is, how many elements, how can I
>> convert it into a sequence of hashes:
>> $ref->{'home'}->{'user'}->{'mail'}
>
> You could use eval() for that, like:
Thanks! Now to see if the idea that this was a solution
to will work.
between asking and being answered I thought up another solution
but that isn't right, so back to this one.
Zebee
------------------------------
Date: Tue, 24 Aug 2004 09:57:17 +0200
From: "Tassilo v. Parseval" <tassilo.von.parseval@rwth-aachen.de>
Subject: Re: convertinga directory path into a hash
Message-Id: <2p0amvFeu1aeU1@uni-berlin.de>
Also sprach Zebee Johnstone:
> I have a unix directory path, say /home/user/mail
>
> Not knowing how long it will be, that is, how many elements, how can I
> convert it into a sequence of hashes:
> $ref->{'home'}->{'user'}->{'mail'}
This can be done with a simple recursive function:
sub path2hash {
my ($p, $ref) = @_;
return if not $p;
my ($head, $tail) = $p =~ m!/?([^/]+)(.*)!;
path2hash($tail, $ref->{ $head } = {});
return $ref;
}
my $ref = path2hash("/home/user/mail");
Note that using string eval (as recommended elsewhere) looks tempting
for a task like this but it can be done just as well (and even more
safely) without.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Tue, 24 Aug 2004 08:16:28 GMT
From: Zebee Johnstone <zebee@zip.com.au>
Subject: Re: convertinga directory path into a hash
Message-Id: <slrncilu0g.fld.zebee@zeus.zipworld.com.au>
In comp.lang.perl.misc on Tue, 24 Aug 2004 09:57:17 +0200
Tassilo v. Parseval <tassilo.von.parseval@rwth-aachen.de> wrote:
> Also sprach Zebee Johnstone:
>
>> I have a unix directory path, say /home/user/mail
>>
>> Not knowing how long it will be, that is, how many elements, how can I
>> convert it into a sequence of hashes:
>> $ref->{'home'}->{'user'}->{'mail'}
>
> This can be done with a simple recursive function:
>
> sub path2hash {
> my ($p, $ref) = @_;
> return if not $p;
> my ($head, $tail) = $p =~ m!/?([^/]+)(.*)!;
> path2hash($tail, $ref->{ $head } = {});
I don't understand what you are passing here, and how the subroutine
sees it.
> return $ref;
> }
>
> my $ref = path2hash("/home/user/mail");
>
> Note that using string eval (as recommended elsewhere) looks tempting
> for a task like this but it can be done just as well (and even more
> safely) without.
>
> Tassilo
--
Zebee Johnstone (zebee@zip.com.au), proud holder of
aus.motorcycles Poser Permit #1.
"Motorcycles are like peanuts... who can stop at just one?"
------------------------------
Date: Tue, 24 Aug 2004 12:55:54 +0200
From: "Tassilo v. Parseval" <tassilo.von.parseval@rwth-aachen.de>
Subject: Re: convertinga directory path into a hash
Message-Id: <2p0l5tFfjqg0U1@uni-berlin.de>
Also sprach Zebee Johnstone:
> In comp.lang.perl.misc on Tue, 24 Aug 2004 09:57:17 +0200
> Tassilo v. Parseval <tassilo.von.parseval@rwth-aachen.de> wrote:
>> Also sprach Zebee Johnstone:
>>
>>> I have a unix directory path, say /home/user/mail
>>>
>>> Not knowing how long it will be, that is, how many elements, how can I
>>> convert it into a sequence of hashes:
>>> $ref->{'home'}->{'user'}->{'mail'}
>>
>> This can be done with a simple recursive function:
>>
>> sub path2hash {
>> my ($p, $ref) = @_;
>> return if not $p;
>> my ($head, $tail) = $p =~ m!/?([^/]+)(.*)!;
>> path2hash($tail, $ref->{ $head } = {});
>
> I don't understand what you are passing here, and how the subroutine
> sees it.
It's a short-cut. More explicitely:
$ref->{ $head } = { };
path2hash($tail, $ref->{ $head });
In Perl, assignments have a return value and that was what I was using
here.
Other than that, it should be pretty straight-forward. Note that this is
a so called primitive recursion because each instantiation of the
function cuts off a piece of its argument ($head) and calls path2hash
with the thusly diminshed argument ($tail).
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Tue, 24 Aug 2004 13:58:35 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: convertinga directory path into a hash
Message-Id: <x7llg4mye1.fsf@mail.sysarch.com>
>>>>> "TvP" == Tassilo v Parseval <tassilo.von.parseval@rwth-aachen.de> writes:
TvP> Also sprach Zebee Johnstone:
>> I have a unix directory path, say /home/user/mail
>>
>> Not knowing how long it will be, that is, how many elements, how can I
>> convert it into a sequence of hashes:
>> $ref->{'home'}->{'user'}->{'mail'}
TvP> sub path2hash {
TvP> my ($p, $ref) = @_;
TvP> return if not $p;
TvP> my ($head, $tail) = $p =~ m!/?([^/]+)(.*)!;
TvP> path2hash($tail, $ref->{ $head } = {});
TvP> return $ref;
TvP> }
TvP> my $ref = path2hash("/home/user/mail");
TvP> Note that using string eval (as recommended elsewhere) looks tempting
TvP> for a task like this but it can be done just as well (and even more
TvP> safely) without.
and i wrote a non-recursive version a long while back in my tutorial on
autovivification:
http://sysarch.com/perl/autoviv.txt
look for deep_hash_assign. you would call it by first splitting the path
on / and passing it the list of dir name parts.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: 23 Aug 2004 03:48:24 -0700
From: l.cleran@free.fr (Lionel)
Subject: Exange of informations and objects between PERL and JAVA
Message-Id: <b7790393.0408230248.729fd01e@posting.google.com>
Hi all,
I would like having more informations on how we could exchange
informations and/or objects between PERL and JAVA.
We have a Java programs that open, maintain and close telnet
connections, for PERL scripts...
Is it possible, to echange the Java telnet session object to PERL
programs ? Or thoses two languages could not exchange objects or such
structure ?
If it's not possible, how could I exchange textual informations
between a Java program and a PERL script on the same UNIX computer ?
Socket, Pipe,... ?
Or mayby, there is another solution ?
Thanks a lot for your help.
Best regards.
Lionel.
------------------------------
Date: 24 Aug 2004 03:13:10 -0700
From: p.krupp@web.de (pk)
Subject: Information exchange between unrelated processes
Message-Id: <320c0c2b.0408240213.5f2a362d@posting.google.com>
Hi!
The Task: There are different unrelated processes which have to
communicate informations. They must be able to read, write and delete
these informations from/to a central entity and it must be guaranteed,
that, while one process is writing, no other one can do the same.
For the moment, this is realized with a file and a locked acces to it.
This works fine, but I guess it is rather slow and uses quite a lot of
resources. So I thought of using shared memory, but in the System V
IPC Section of the Camel-Book I find some arguments against it.
So what would we an apropriate technique?
Thanks: Peter
------------------------------
Date: Mon, 23 Aug 2004 16:45:52 +0100
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: perl interpreter automatically exit windows so how I can saw the result of script?
Message-Id: <g2gpv1-9t5.ln1@osiris.mauzo.dyndns.org>
Quoth Joe Smith <Joe.Smith@inwap.com>:
> Jeff 'japhy' Pinyan wrote:
>
> > On Thu, 19 Aug 2004, Greg Bacon wrote:
> >
> >>I like to use something similar to the following:
> >>
> >> END { system "pause" unless $ENV{PROMPT} }
> >>
> >>That way, I don't see the pause in a command window.
> >>
> >>I'd like to know of a workaround that would cause the window to
> >>linger when there are syntax errors, a use fails, etc.
> >
> > Easy: make that END { ... } the first line of your code.
>
> Nope, that doesn't work. END only works after INIT time, and that
> does not happen on compile errors.
Catch $SIG{__DIE__}, perhaps? (untested)
BEGIN {
$SIG{__DIE__} = sub {
# fix bizarre calls to __DIE__ in evals
die @_ if $^S or $ENV{PROMPT};
warn @_;
system 'pause';
};
}
Ben
--
Outside of a dog, a book is a man's best friend.
Inside of a dog, it's too dark to read.
ben@morrow.me.uk Groucho Marx
------------------------------
Date: Tue, 24 Aug 2004 02:23:04 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <S6WdnfGHF6dFcbfcRVn-hA@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: Tue, 24 Aug 2004 06:34:59 -0400
From: "Mike Lepore" <lepor5e@bestweb.net>
Subject: split question
Message-Id: <10im66m6ks8qf3@corp.supernews.com>
Not sure whether this is a split question or a regex question (newbie).
Given a string variable which contains at least one space character,
how can I extract everything to the left of the first space,
and everything to the right of the first space?
The number of characters and fields can't be hardcoded.
Example:
$Variable = "abc def ghi jkl";
$Variable1 become "abc" and $Variable2 becomes "def ghi jkl"
Thank you for your time.
Mike Lepore, email delete the 5, lepore at bestweb dot net
------------------------------
Date: Tue, 24 Aug 2004 12:37:53 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: split question
Message-Id: <2p0k6qFfcfc8U1@uni-berlin.de>
Mike Lepore wrote:
> Not sure whether this is a split question or a regex question
> (newbie). Given a string variable which contains at least one space
> character, how can I extract everything to the left of the first
> space, and everything to the right of the first space?
> The number of characters and fields can't be hardcoded.
> Example:
> $Variable = "abc def ghi jkl";
> $Variable1 become "abc" and $Variable2 becomes "def ghi jkl"
Can be done either with a regex or the split() function, but split()
is probably best suited for the task.
perldoc -f split
> Thank you for your time.
You're welcome.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Tue, 24 Aug 2004 10:57:06 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: split question
Message-Id: <6aFWc.2332$A8.1647@edtnps89>
Mike Lepore wrote:
> Not sure whether this is a split question or a regex question (newbie).
> Given a string variable which contains at least one space character,
> how can I extract everything to the left of the first space,
> and everything to the right of the first space?
> The number of characters and fields can't be hardcoded.
> Example:
> $Variable = "abc def ghi jkl";
> $Variable1 become "abc" and $Variable2 becomes "def ghi jkl"
Well, since split uses a regex, that is a moot question. :-)
( $Variable1, $Variable2 ) = $Variable =~ /(\S+)\s+(.+)/;
Or:
( $Variable1, $Variable2 ) = split ' ', $Variable, 2;
John
--
use Perl;
program
fulfillment
------------------------------
Date: Tue, 24 Aug 2004 15:44:37 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: split question
Message-Id: <pan.2004.08.24.13.44.37.37680@aursand.no>
On Tue, 24 Aug 2004 06:34:59 -0400, Mike Lepore wrote:
> Given a string variable which contains at least one space character,
> how can I extract everything to the left of the first space,
> and everything to the right of the first space?
> The number of characters and fields can't be hardcoded.
> Example:
> $Variable = "abc def ghi jkl";
> $Variable1 become "abc" and $Variable2 becomes "def ghi jkl"
Untested:
#!/usr/bin/perl
#
use strict;
use warnings;
use Data::Dumper;
my $string = 'abc def ghi jkl';
my @parts = split( /\s+/, $string, 2 );
print Dumper( \@parts );
--
Tore Aursand <tore@aursand.no>
"Leadership is doing what is right when no one is watching." (George
Van Valkenburg)
------------------------------
Date: Tue, 24 Aug 2004 15:58:43 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: split question
Message-Id: <2p100bFffgb9U1@uni-berlin.de>
Tore Aursand wrote:
>
> Untested:
>
> #!/usr/bin/perl
> #
> use strict;
> use warnings;
> use Data::Dumper;
>
> my $string = 'abc def ghi jkl';
> my @parts = split( /\s+/, $string, 2 );
>
> print Dumper( \@parts );
Why on earth do you use Data::Dumper to print a two elements array?
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Tue, 24 Aug 2004 10:25:52 -0400
From: "Rafal Konopka" <rafalk@comcast.net>
Subject: Re: split question
Message-Id: <OKOdnXxPSMH3zbbcRVn-rw@comcast.com>
"Mike Lepore" <lepor5e@bestweb.net> wrote in message
news:10im66m6ks8qf3@corp.supernews.com...
> Not sure whether this is a split question or a regex question (newbie).
> Given a string variable which contains at least one space character,
> how can I extract everything to the left of the first space,
> and everything to the right of the first space?
> The number of characters and fields can't be hardcoded.
> Example:
> $Variable = "abc def ghi jkl";
> $Variable1 become "abc" and $Variable2 becomes "def ghi jkl"
Yet another syntactic variant:
( $Variable1, $Variable2 ) = map {$`,$'} $Variable =~ /\s+/;
Rafal
------------------------------
Date: Tue, 24 Aug 2004 14:36:00 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: split question
Message-Id: <x7wtzoli38.fsf@mail.sysarch.com>
>>>>> "RK" == Rafal Konopka <rafalk@comcast.net> writes:
RK> Yet another syntactic variant:
RK> ( $Variable1, $Variable2 ) = map {$`,$'} $Variable =~ /\s+/;
GACK!!!
that has to be one of the worst (i assume you are serious and you use
it) idioms to split on white space i have ever seen.
have you never read why using those special variables are bad?
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: Tue, 24 Aug 2004 14:39:31 GMT
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: split question
Message-Id: <DqIWc.4336$oD2.4118@trndny08>
"Rafal Konopka" <rafalk@comcast.net> wrote in message
news:OKOdnXxPSMH3zbbcRVn-rw@comcast.com...
> "Mike Lepore" <lepor5e@bestweb.net> wrote in message
> news:10im66m6ks8qf3@corp.supernews.com...
> > Not sure whether this is a split question or a regex question (newbie).
> > Given a string variable which contains at least one space character,
> > how can I extract everything to the left of the first space,
> > and everything to the right of the first space?
> > The number of characters and fields can't be hardcoded.
> > Example:
> > $Variable = "abc def ghi jkl";
> > $Variable1 become "abc" and $Variable2 becomes "def ghi jkl"
>
> Yet another syntactic variant:
>
> ( $Variable1, $Variable2 ) = map {$`,$'} $Variable =~ /\s+/;
Not only is that a perverse means of using map {}, you're also using
variables that shouldn't be used unless absolutely necessary. The pre-match
and post-match built-ins impose a performance hit on all regular expressions
when used even once. Read
perldoc perlvar
perldco perlre
for more info.
Paul Lalli
------------------------------
Date: 24 Aug 2004 14:55:37 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: split question
Message-Id: <Xns954F6F27D6D12asu1cornelledu@132.236.56.8>
Gunnar Hjalmarsson <noreply@gunnar.cc> wrote in news:2p100bFffgb9U1@uni-
berlin.de:
> Tore Aursand wrote:
>>
>> Untested:
>>
>> #!/usr/bin/perl
>> #
>> use strict;
>> use warnings;
>> use Data::Dumper;
>>
>> my $string = 'abc def ghi jkl';
>> my @parts = split( /\s+/, $string, 2 );
>>
>> print Dumper( \@parts );
>
> Why on earth do you use Data::Dumper to print a two elements array?
Why not? The
print Dumper $var;
call is the same no matter what data structure you are using so that is one
less thing to worry about especially when debugging.
Sinan.
------------------------------
Date: Tue, 24 Aug 2004 17:04:33 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: split question
Message-Id: <pan.2004.08.24.15.04.33.111424@aursand.no>
On Tue, 24 Aug 2004 15:58:43 +0200, Gunnar Hjalmarsson wrote:
>> use Data::Dumper;
>>
>> my $string = 'abc def ghi jkl';
>> my @parts = split( /\s+/, $string, 2 );
>>
>> print Dumper( \@parts );
> Why on earth do you use Data::Dumper to print a two elements array?
Why not? I always have Data::Dumper in my scripts (when I develop), and
that way I don't have to care _ever_ what structure my data has.
You have a valid point, though; There is no explicit need in this case,
but that's no reason to not use Data::Dumper.
It's one of my favourite modules, by the way. Along with CGI.pm, of
course. :)
--
Tore Aursand <tore@aursand.no>
"I know not with what weapons World War 3 will be fought, but World War
4 will be fought with sticks and stones." (Albert Einstein)
------------------------------
Date: 24 Aug 2004 04:24:35 -0700
From: kngnsm@yahoo.com (kngnsm)
Subject: Using perl and wmi to get MS file version info
Message-Id: <df210ef7.0408240324.274ac6ba@posting.google.com>
As anyone figured out how to get the file version info of a *specified
file* using perl and wmi?
Scriptomatic gives you the following but returns every file from the
directory WINNT - I want to be able to specify the file I whose info I
want.
On Error Resume Next
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer &
"\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from
Win32_FileSpecification",,48)
For Each objItem in colItems
Wscript.Echo "Attributes: " & objItem.Attributes
Wscript.Echo "Caption: " & objItem.Caption
Wscript.Echo "CheckID: " & objItem.CheckID
Wscript.Echo "CheckMode: " & objItem.CheckMode
Wscript.Echo "CheckSum: " & objItem.CheckSum
Wscript.Echo "CRC1: " & objItem.CRC1
Wscript.Echo "CRC2: " & objItem.CRC2
Wscript.Echo "CreateTimeStamp: " & objItem.CreateTimeStamp
Wscript.Echo "Description: " & objItem.Description
Wscript.Echo "FileID: " & objItem.FileID
Wscript.Echo "FileSize: " & objItem.FileSize
Wscript.Echo "Language: " & objItem.Language
Wscript.Echo "MD5Checksum: " & objItem.MD5Checksum
Wscript.Echo "Name: " & objItem.Name
Wscript.Echo "Sequence: " & objItem.Sequence
Wscript.Echo "SoftwareElementID: " & objItem.SoftwareElementID
Wscript.Echo "SoftwareElementState: " &
objItem.SoftwareElementState
Wscript.Echo "TargetOperatingSystem: " &
objItem.TargetOperatingSystem
Wscript.Echo "Version: " & objItem.Version
Next
------------------------------
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 6904
***************************************
