[22880] in Perl-Users-Digest
Perl-Users Digest, Issue: 5101 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jun 10 06:06:02 2003
Date: Tue, 10 Jun 2003 03: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, 10 Jun 2003 Volume: 10 Number: 5101
Today's topics:
Added apache_md5_crypt to create a valid hash for use (Kio)
Re: exclude a word using regexp (paaro)
Re: How to I arrange for a socket connection to time ou <gmiller@NOTforSPAM.gregmiller.net>
Re: passing argvs to interactive program (perl wrapper) <nobull@mail.com>
Re: Perl CGI and Downloading Files - How? <flavell@mail.cern.ch>
Re: Perl CGI and Downloading Files - How? 10ghz@radiate.com
Possible to read a binary file into a scalar variable? <SeeMessageBody@nospam.com>
Re: Possible to read a binary file into a scalar variab <mbudash@sonic.net>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Probelm with PERL and Informix Can't use string ("I <bigj@kamelfreund.de>
Re: Sorting and formatting (Jay Tilton)
Re: What happens with $1 in a second regexp (was: Quick <bigj@kamelfreund.de>
Win32::ListView sample please?? (Kenjis Kaan)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 10 Jun 2003 00:14:54 -0700
From: kioweb@tutopia.com (Kio)
Subject: Added apache_md5_crypt to create a valid hash for use in .htpasswd files
Message-Id: <5d201602.0306092314.40341f7@posting.google.com>
First, a little explanation
I'm webmaster, my work method is duplicate my remote host
(Apache+Perl+Php+MySql+Unix systems) in my local PC
(ApacheWin32+ActiveStatePerl+php_win32+MySql win32+Win98SE), and work
very fine !!!
However there are some few things to those that I have not found
solution.
This is the problem:
Added apache_md5_crypt to create a valid hash for use in .htpasswd
files ?
Apache for Windows include a binary called htpasswd.exe for generate
valid username:password values
In Windows systems Apache Authentification only support MD5
encryption.
Example:
E:\Apache\bin>htpasswd.exe -c password.txt Administrator
Automatically using MD5 format on Windows.
New password: *****
Re-type new password: *****
Adding password for user Administrator
the results in password.txt is: (value1)
Administrator:$apr1$8Z/.....$5g6gHGfU531HsIx4p7Ehl/
(the password is "spurs")
this file format run ok for .htaccess in windows and unix systems
I read Perl docs and download and install Crypt::PasswdMD5: Module to
provide an interoperable crypt() to create the same
file format with a cgi Script, something like this
#!/usr/local/bin/perl
use Crypt::PasswdMD5;
$name = "Administrator";
$password = "spurs";
$cryptedpassword = apache_md5_crypt($password, $salt);
print "$name:$cryptedpassword";
now running E:\Apache\bin>perl m.pl
the result is: (value2)
Administrator:$apr1$$S44y93.qPKhwCOnmVpqbN1
But this values don't work in Apache Auth
obviously the format of the value1 and value2 are not equals
Somebody knows as writing the script correctly so that it generates
values like those that Windows needs (with or without PasswdMD5.pm)
Thanks
Guillermo
------------------------------
Date: 10 Jun 2003 01:43:57 -0700
From: paaro@hockeymail.com (paaro)
Subject: Re: exclude a word using regexp
Message-Id: <c7395c40.0306100043.12dba683@posting.google.com>
Thanks to all of you.
I'm considering using an HTML module. The question itself was more of
a general nature, that is, how to find specific portions of text which
don't contain specific word or words.
Thanks,
Paaro
tadmc@augustmail.com (Tad McClellan) wrote in message news:<slrnbe92a7.h3i.tadmc@magna.augustmail.com>...
> paaro <paaro@hockeymail.com> wrote:
>
> > I have a following problem: I read a HTML file into a variable,
>
>
> You should use a module that understand HTML for processing HTML.
>
>
> > then I want to find all links (<a ....>...</a>) and check whether they
> > have an attribute "target". If they don't, then I want to add
> > target="_blank".
>
>
> > Any ideas of how to exclude particular word?
>
>
> A regex approach is bound to be sub-optimal compared to a module
> that does a Real Parse, but here is a fragile regex "solution":
>
> s{(<a.*?>)}
> {
> my $a = $1;
> unless ( $a =~/\btarget\s*=/ )
> { substr($a, -1, 0) = ' target="_blank"' }
> $a;
> }ige;
------------------------------
Date: Tue, 10 Jun 2003 04:49:12 GMT
From: Greg Miller <gmiller@NOTforSPAM.gregmiller.net>
Subject: Re: How to I arrange for a socket connection to time out?
Message-Id: <inoaev4i7b0gi5otf74ug90tc5qvg3cnfn@4ax.com>
On 9 Jun 2003 19:47:12 -0400, jbrock@panix.com (John Brock) wrote:
>What I ended up doing was using the send() and recv() methods of
>IO::Socket for all socket communication, and using the can_read()
>method of IO:Select to set timeouts. This seems to work, but of
>course I need to do more testing.
Sorry, my last post was incorrect, I use recv() not read() as
I stated before. So you should be fine now.
Greg Miller (gmiller at gregmiller dot net)
http://www.gregmiller.net
http://www.net-chess.com
------------------------------
Date: 10 Jun 2003 08:48:00 +0100
From: Brian McCauley <nobull@mail.com>
Subject: Re: passing argvs to interactive program (perl wrapper)
Message-Id: <u9llwaz83z.fsf@wcl-l.bham.ac.uk>
dwlepage@yahoo.com (david) writes:
> I want to write a shell wrapper for 'login' on Solaris, but written in
> perl. Could someone point me in the direction of how to interact with
> an interactive program?
I _Expect_ you'll find something on CPAN (or even in the FAQ) to help.
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Tue, 10 Jun 2003 11:03:09 +0200
From: "Alan J. Flavell" <flavell@mail.cern.ch>
Subject: Re: Perl CGI and Downloading Files - How?
Message-Id: <Pine.LNX.4.53.0306101054560.27642@lxplus006.cern.ch>
On Tue, Jun 10, 10ghz@radiate.com inscribed on the eternal scroll:
> Hmm... Now that is interesting. Why is it "Expensive"?
CGI. Nuff said.
> >And this still isn't a question about Perl, specifically.
>
> Did you understand the part where I mentioned "Using Perl"?
Sure - in fact I think just about every regular reader around here
understood it.
Stick around; I'm sure you'll grasp the concept after a while.
Until we've established what the task is meant to be, there's little
sense in discussing the specifics of the Perl language.
(Of course you -have- now gone some way to repair that deficit, by
explaining a little more about your purpose. But you're still at the
stage of doing the systems analysis of a WWW task, rather than
actually programming it in Perl yet. Seems to me that once you've
decided what you want to do, the actual Perl coding would be trivial.)
Good luck.
------------------------------
Date: Tue, 10 Jun 2003 09:55:26 GMT
From: 10ghz@radiate.com
Subject: Re: Perl CGI and Downloading Files - How?
Message-Id: <il9bevoj8h1l2ral3dh2qa7t8dhv3ab8om@4ax.com>
On Tue, 10 Jun 2003 11:03:09 +0200, "Alan J. Flavell" <flavell@mail.cern.ch>
wrote:
>Until we've established what the task is meant to be, there's little
>sense in discussing the specifics of the Perl language.
Yes, I guess it's hard to understand that I want my Perl script to send a file.
I guess newbies find that a difficult concept.
>(Of course you -have- now gone some way to repair that deficit, by
>explaining a little more about your purpose. But you're still at the
>stage of doing the systems analysis of a WWW task, rather than
>actually programming it in Perl yet.
Funny, I have 99% of it coded in Perl already. I'm just having the Perl script
send the file. But, you said that was such an inefficient method. But you never
elaborated on other possibilities. Too bad, I thought you might have something
to add but I guess not.
>Good luck.
Gee, thanks!
Molon Labe!
------------------------------
Date: Tue, 10 Jun 2003 04:44:49 GMT
From: "John" <SeeMessageBody@nospam.com>
Subject: Possible to read a binary file into a scalar variable?
Message-Id: <5ndFa.38652$rO.3634375@newsread1.prod.itd.earthlink.net>
This only loads the *first line* of a text file:
my $file = <FILE>; # I'd rather do this, but it doesn't work.
Now this reads the entire text file, but into an array:
my @lines = <FILE>;
...which I then run through a one-way hash function to generate a hash code
(or message digest, or checksum, or whatever you prefer to call it).
Passing the array of a file's lines to the function works fine for text
files like scripts, but for binary files it isn't working: some of the hash
codes from a few different binary files come out the same. I suspect that
only the first few bits are being read, and these are identical for some of
these.
Is it possible to read a binary file into some scalar variable? That is the
problem.
I intend to use this little beauty to "fingerprint" my files on multi-user
systems (Unix hosts) and check 'em periodically to make sure they haven't
been tampered with. I planned on store the file name / hash code pairs into
an Oracle table on my PC, but now I see something about DBM files toward the
end of that most *EXCELLENT* book "Learning Perl" by Schwartz and Phoenix,
so I might try DBM files.
I sleep with that book. It's the crown jewel of Perl books and one of
mankind's highest literary achievements. When I will wear it out I will buy
another.
--
------------------------------------------------
Feel free to mail me: workingstiff19
...and that's at hotmail.
------------------------------
Date: Tue, 10 Jun 2003 04:58:57 GMT
From: Michael Budash <mbudash@sonic.net>
Subject: Re: Possible to read a binary file into a scalar variable?
Message-Id: <mbudash-112E2B.21590509062003@typhoon.sonic.net>
In article <5ndFa.38652$rO.3634375@newsread1.prod.itd.earthlink.net>,
"John" <SeeMessageBody@nospam.com> wrote:
> This only loads the *first line* of a text file:
>
> my $file = <FILE>; # I'd rather do this, but it doesn't work.
>
> Now this reads the entire text file, but into an array:
>
> my @lines = <FILE>;
>
> ...which I then run through a one-way hash function to generate a hash code
> (or message digest, or checksum, or whatever you prefer to call it).
> Passing the array of a file's lines to the function works fine for text
> files like scripts, but for binary files it isn't working: some of the hash
> codes from a few different binary files come out the same. I suspect that
> only the first few bits are being read, and these are identical for some of
> these.
>
> Is it possible to read a binary file into some scalar variable? That is the
> problem.
try:
open (FILE, 'thefile') or die ("Can't open thefile: $!");
binmode (FILE);
my $file = do { local $/; <FILE>; };
--
Michael Budash
------------------------------
Date: Tue, 10 Jun 2003 02:22:43 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <vIKdnWkcfqDeGnijRTvU3Q@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.4 $)
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.
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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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, 10 Jun 2003 08:05:30 +0200
From: "Janek Schleicher" <bigj@kamelfreund.de>
Subject: Re: Probelm with PERL and Informix Can't use string ("Informix") as a HASH ref
Message-Id: <pan.2003.06.10.05.54.32.959782@kamelfreund.de>
Chavan Koya wrote at Mon, 09 Jun 2003 16:07:18 -0700:
> I am getting a error message when i call a perl program from
> a shell script. We have no problem with older version. but we are
> upgrading and doing server consolidation (i.e right now there is one
> production box this has old version of perl and we installed new
> version on new production box )I no nothing about PERL. Please give me
> some suggestions on this problem
>
> ${$dbattr}{AutoCommit} = 1 if (!defined ${$dbattr}{AutoCommit}); #
> line # 146
Have you also tried
$dbattr->{AutoCommit} = 1 if ...
Greetings,
Janek
------------------------------
Date: Tue, 10 Jun 2003 04:55:21 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: Sorting and formatting
Message-Id: <3ee562c2.539898834@news.erols.com>
satishi@gwu.edu (slash) wrote:
: Following is the output I have from the above sorting:
: * * * united
: 16 april 16 2002
: 2002 16 2002 method
[snip]
: As you can see first and the third columns are same, whereas second
: and fourth columns represent occurrences of words associated with each
: word in first and third columns. In other words, all occurrences of
: the string "*" are "*" and "united".
:
: What I would like to do is to be able to represent the output in the
: following way:
:
: * *
: * united
for( @data ) {
printf "%s\t%s\n%s\t%s\n", split;
}
: Can I take this a step further and store it as:
:
: * *, united
for( @data ) {
printf "%s\t%s, %s\n", (split)[0, 1, 3];
}
------------------------------
Date: Tue, 10 Jun 2003 08:05:30 +0200
From: "Janek Schleicher" <bigj@kamelfreund.de>
Subject: Re: What happens with $1 in a second regexp (was: Quick question)
Message-Id: <pan.2003.06.10.05.59.47.941454@kamelfreund.de>
Avatar wrote at Mon, 09 Jun 2003 14:00:16 -0700:
> $search=~/(.*)blah/;
> I know that .* gets placed into $1.
> $search2=~/(.*)blah/;
> Does that overwrite the orginal $1, append onto it, or cause an error?
overwrite
$1, $2, $3, ... are _global_ variables
that are assigned new in every new regexp.
For details, please read
perldoc perlre
Greetings,
Janek
------------------------------
Date: 9 Jun 2003 23:48:20 -0700
From: tivolinewbie@canada.com (Kenjis Kaan)
Subject: Win32::ListView sample please??
Message-Id: <6a8ba9f8.0306092248.78b6263c@posting.google.com>
Hi, I am trying to create a listview program but no matter what I do
its is not working. I wonder if its because of the activestate perl
(5.6.1) I am using. I can open up a win32 window but the listview
just isn't what I wanted.
I need to use ListView in order to display multiple rows of data
extracted from a DB2 database. Trying to make a nice little report of
data in DB2.
Can someone give me a working example of ListView? prefereable one
that also set the text/backgroun color to non-defaults. TIA
------------------------------
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.
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 5101
***************************************
