[24606] in Perl-Users-Digest
Perl-Users Digest, Issue: 6782 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jul 9 09:05:58 2004
Date: Fri, 9 Jul 2004 06:05:06 -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 Fri, 9 Jul 2004 Volume: 10 Number: 6782
Today's topics:
Re: Secure Database Systems <ron@savage.net.au>
Re: hash as argument <Joe.Smith@inwap.com>
Re: hash as argument <spamtrap@dot-app.org>
Re: hash as argument <ahamm@mail.com>
Re: hash as argument <spamtrap@dot-app.org>
Re: hash as argument <daedalus@videotron.ca>
Re: hash as argument (Anno Siegel)
Re: Looping through hash for match and replacement stri <Joe.Smith@inwap.com>
Re: Looping through hash for match and replacement stri (Anno Siegel)
Re: Perl newbie please help <krahnj@acm.org>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Regexp substitution problem - suggestions? <jhalbrook@bjc.org>
Re: Regexp substitution problem - suggestions? <bernard.el-haginDODGE_THIS@lido-tech.net>
Re: What does this do? <abigail@abigail.nl>
Re: What does this do? (Peter J. Acklam)
Re: What does this do? <vek@station02.ohout.pharmapartners.nl>
Re: What does this do? <pinyaj@rpi.edu>
XSLT Transformation <axel@strube-zettler.de>
Re: XSLT Transformation <regner@dievision.de>
Re: XSLT Transformation <vetro@online.no>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 9 Jul 2004 18:25:39 +1000
From: Ron Savage <ron@savage.net.au>
Subject: Re: Secure Database Systems
Message-Id: <200479182539.091064@ron>
On Fri, 9 Jul 2004 16:41:37 +1000, Sarah Tanembaum wrote:
Hi Sarah
Frankly, I'd skip the db route at this time and go to=
http://www.treepad.com/
The business version has encryption built in. There is a freeware version=
(TreePad Lite) to tryout.
--
Cheers
Ron Savage, ron@savage.net.au on 9/07/2004
http://savage.net.au/index.html
------------------------------
Date: Fri, 09 Jul 2004 07:11:50 GMT
From: Joe Smith <Joe.Smith@inwap.com>
Subject: Re: hash as argument
Message-Id: <WyrHc.52541$XM6.41600@attbi_s53>
Sherm Pendley wrote:
> And don't use double-quotes on strings unless it's necessary.
Has Larry Wall made a statement on this?
Using double quotes in a situation where single quotes could also
be used is not a programming error. It is a matter of style.
-Joe
------------------------------
Date: Fri, 09 Jul 2004 03:39:48 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: hash as argument
Message-Id: <efadnTtZu6BY1nPd4p2dnA@adelphia.com>
Joe Smith wrote:
> Has Larry Wall made a statement on this?
I think his statement that "there's more than one way to do it" is relevant.
Quite a shame so many folks have forgotten it.
> It is a matter of style.
I agree, but there are a few regulars here who view it as a matter of
religion. Minimizing the use of double-quotes, at least when posting code
here, helps reduce the incessant whining about it.
I'd fight the good fight if it mattered, but in this case there's nothing to
be gained by arguing the point.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Fri, 9 Jul 2004 18:00:56 +1000
From: "Andrew Hamm" <ahamm@mail.com>
Subject: Re: hash as argument
Message-Id: <2l71m2F9i40sU1@uni-berlin.de>
Sherm Pendley wrote:
> Joe Smith wrote:
>
>> Has Larry Wall made a statement on this?
>
> I think his statement that "there's more than one way to do it" is
> relevant. Quite a shame so many folks have forgotten it.
>
>> It is a matter of style.
>
> I agree, but there are a few regulars here who view it as a matter of
> religion. Minimizing the use of double-quotes, at least when posting
> code here, helps reduce the incessant whining about it.
>
I'm not changing - I hate it when I spend 15 minutes looking for a bug only
to finally discover I've tried to add $thingy inside single quotes. Too he11
with that...
------------------------------
Date: Fri, 09 Jul 2004 05:40:13 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: hash as argument
Message-Id: <uY-dnckOfONg-nPdRVn_iw@adelphia.com>
Andrew Hamm wrote:
> I'm not changing
So now someone wants to debate whether it's a subject worth arguing about.
Oy! You just can't win with this group...
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Fri, 9 Jul 2004 08:07:16 -0400
From: "Daedalus" <daedalus@videotron.ca>
Subject: Re: hash as argument
Message-Id: <qRvHc.40515$_p5.872253@wagner.videotron.net>
> So now someone wants to debate whether it's a subject worth arguing about.
> Oy! You just can't win with this group...
Arguing on programming habits and style is pretty trivial... in both
direction.
We could say that uses of double-quotes should only be prefered when their
behavior is needed, but we could also say that uses of single-quote should
only be prefered when their behavior is needed. Double-quotes make it easier
to add variables or backslash-escapes, while single-quote make it clearer
that there's no interpolation. To me their uses are a matter of choice. But
saying "misuse of double-quotes" or ask to "fix" the thing... Do it because
the majority is doing it, thats not a rule of perl.
Pointing to the fact that many people would not even look at the code
because they don't like the "prefer double-quote" style is fine, it's good
to know, but asking someone to fix something that is not broken is another.
It's not like the thing is an ancien obscur use like using $mains'var
instead of $main::var. "If it ain't broke don't fix it".
It's an opinion, you people are free to like it or not, but it's mine and
I'm free to have it.
DAE
------------------------------
Date: 9 Jul 2004 12:43:27 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: hash as argument
Message-Id: <ccm3tf$9ra$1@mamenchi.zrz.TU-Berlin.DE>
Daedalus <daedalus@videotron.ca> wrote in comp.lang.perl.misc:
> > So now someone wants to debate whether it's a subject worth arguing about.
> > Oy! You just can't win with this group...
>
>
> Arguing on programming habits and style is pretty trivial... in both
> direction.
> We could say that uses of double-quotes should only be prefered when their
> behavior is needed, but we could also say that uses of single-quote should
> only be prefered when their behavior is needed. Double-quotes make it easier
> to add variables or backslash-escapes, while single-quote make it clearer
> that there's no interpolation. To me their uses are a matter of choice. But
> saying "misuse of double-quotes" or ask to "fix" the thing... Do it because
> the majority is doing it, thats not a rule of perl.
It is a more general rule of human interaction. It is often useful
to do things in one, agreed-upon way, even if there is no rational
reason why that particular way should be preferred. Traffic regulations
(beginning with the side of the road you drive on) are often quite
arbitrary, but the advantages of adhering to them are obvious.
Similarly, for a programming community, there are advantages in having
conventional preferences for one style over another when technically
two (or more) ways would give the same result. By using the conventional
style, the author tells the reader "Nothing to see here, move along...".
A deviation from the standard tells the reader to look for the reason.
That makes such code a lot easier to read.
Thus, a set of stylistic conventions gives a language a dimension of
expressiveness it wouldn't have without it. That is a Good Thing.
The preference of '' over "" and of sub() over &sub belong in this
category.
> Pointing to the fact that many people would not even look at the code
> because they don't like the "prefer double-quote" style is fine, it's good
> to know, but asking someone to fix something that is not broken is another.
> It's not like the thing is an ancien obscur use like using $mains'var
> instead of $main::var. "If it ain't broke don't fix it".
It's not about "correct" or "broken", it's about clarity.
Anno
------------------------------
Date: Fri, 09 Jul 2004 07:48:59 GMT
From: Joe Smith <Joe.Smith@inwap.com>
Subject: Re: Looping through hash for match and replacement strings
Message-Id: <L5sHc.47252$%_6.8123@attbi_s01>
Driver wrote:
> With the included code, I'm trying to:
>
> -- parse a mif file
> -- match the left side string of the %op hash (index) with occurances of
> that string in the mif file
> -- replace the matched string with the string on the right side of the %op
> hash (keys)
The program you posted has a much different flow of logic.
repeat 37 times {
open "anyfile.mif" for reading and "anyfile.mif.new" for writing.
read entire file, make at most one substitution per line, write line out.
}
It is very inefficient to read the input file 37 times.
Since the output file is clobbered each time through the loop, any
previous substitutions will be thrown away; only the last set of
substitutions end up in the final output file.
A better approach would be to build a complex search string and substitute
from the hash using a single pass through the input file.
$search = join '|',keys %op;
while(<>) {
s/($search)/$op{$1}/g;
print;
}
------------------------------
Date: 9 Jul 2004 11:35:34 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Looping through hash for match and replacement strings
Message-Id: <cclvu6$77m$1@mamenchi.zrz.TU-Berlin.DE>
Joe Smith <Joe.Smith@inwap.com> wrote in comp.lang.perl.misc:
> Driver wrote:
>
> > With the included code, I'm trying to:
> >
> > -- parse a mif file
> > -- match the left side string of the %op hash (index) with occurances of
> > that string in the mif file
> > -- replace the matched string with the string on the right side of the %op
> > hash (keys)
>
> The program you posted has a much different flow of logic.
> repeat 37 times {
> open "anyfile.mif" for reading and "anyfile.mif.new" for writing.
> read entire file, make at most one substitution per line, write line out.
> }
>
> It is very inefficient to read the input file 37 times.
> Since the output file is clobbered each time through the loop, any
> previous substitutions will be thrown away; only the last set of
> substitutions end up in the final output file.
Very true. The program has more problems, such as the liberal use of
barewords, undeclared variables, and use of uninitialized values.
Most of these would have been caught by warnings and strict.
> A better approach would be to build a complex search string and substitute
> from the hash using a single pass through the input file.
>
> $search = join '|',keys %op;
> while(<>) {
> s/($search)/$op{$1}/g;
> print;
> }
In general this approach requires the keys to be sorted so that long
keys come before short ones. Otherwise, if one key is a substring of
another, you may get spurious substitutions. Also, in case a key
contains regex-specific characters, it is prudent to quotemeta the
keys.
$search = join '|', map quotemeta,
sort { length $b <=> length $a } keys %op;
With the given data, both of these operations are no-ops, but data
can change.
Anno
------------------------------
Date: Fri, 09 Jul 2004 10:36:12 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: Perl newbie please help
Message-Id: <40EE7505.67FCDE6C@acm.org>
Paul Lalli wrote:
>
> On Thu, 8 Jul 2004, Jordy Keighan wrote:
> >
> > @user_array = split(" ", $user_string);
>
> Why are you doing this? Why are you composing one large string, manually
> separating each field with spaces, and then using split to get an array
> back out? Unless you're using $user_string later in unshown code (and if
> you are, feel free to ignore me here), conider changing this to:
> my @user_array;
> foreach my $key ($doc->getElementsByTagName('credentials')){
> push @user_array, $key->getAttribute('name');
> }
>
> > print $user_array[0]; # VALUE OK prints bob!!!!
>
> out of curiousity, does it really print *just* bob? Or does the value
> perhaps have extra whitespace attached to either end?
It can't have any whitespace as the previous line removes all
whitespace.
John
--
use Perl;
program
fulfillment
------------------------------
Date: Fri, 09 Jul 2004 02:22:07 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <jsKdnZ7rGc4C2nPdRVn-ig@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: Fri, 9 Jul 2004 07:14:46 -0500
From: "JK" <jhalbrook@bjc.org>
Subject: Regexp substitution problem - suggestions?
Message-Id: <10et31f4ecdopce@corp.supernews.com>
I need to search for all occurrences of mailto tags in a file, and hyperlink
them.
i.e.
mailto:jim@his-domain.com
to:
<a href="mailto:jim@his-domain.com">mailto:jim@his-domain.com</a>
I currently have been trying to use this code (excuse the coding, I'm a Perl
newbie):
####
foreach (@lines) {
if ($_ =~ /mailto/ig) {
if ($_ =~ /href=/ig) {
} else {
my $str = index($_,"mailto");
my $endstr = index($_," ",$str);
if ($endstr < 0) {
my $len = length($_) - $str;
$len++;
} else {
my $len = ($_ - $str);
}
my $parm1 = substr($_,$str,$len);
$_ =~ s/$parm1/<a href="$parm1">$parm1<\/a>/ig; #
This is the problem line
}
}
}
####
When I display $parm1, I get the entire mailto tag, but when I display
the value of $_ I don't get the hyperlinked version that I want. It is
unchanged.
I'm sure there's a much more efficient way to do this. :-)
Joe
------------------------------
Date: Fri, 9 Jul 2004 14:28:45 +0200
From: "Bernard El-Hagin" <bernard.el-haginDODGE_THIS@lido-tech.net>
Subject: Re: Regexp substitution problem - suggestions?
Message-Id: <Xns952193A566965elhber1lidotechnet@62.89.127.66>
"JK" <jhalbrook@bjc.org> wrote:
> I need to search for all occurrences of mailto tags in a file, and
> hyperlink them.
>
> i.e.
>
> mailto:jim@his-domain.com
>
> to:
>
> <a href="mailto:jim@his-domain.com">mailto:jim@his-domain.com</a>
>
> I currently have been trying to use this code (excuse the coding,
> I'm a Perl newbie):
As long as what's after "mailto" contains no whitespaces you can use:
s/(mailto:\S+?)/<a href="$1">$1</a>/g;
--
Cheers,
Bernard
------------------------------
Date: 09 Jul 2004 08:18:07 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: What does this do?
Message-Id: <slrncesl5v.4g9.abigail@alexandra.abigail.nl>
gnari (gnari@simnet.is) wrote on MMMCMLXIV September MCMXCIII in
<URL:news:ccklsq$v2f$1@news.simnet.is>:
!! "Jeff 'japhy' Pinyan" <pinyaj@rpi.edu> wrote in message
!! news:Pine.SGI.3.96.1040708181456.48121A-100000@vcmr-64.server.rpi.edu...
!! >
!! > $|, as defined by the internal magic supporting it, is set to 0 when given
!! > a false value, and 1 when given ANY true value.
!!
!! in that case the $|++ does not even have the advantage
!! of allowing us to 'localize' the value as in:
!!
!! # unknown $| state
!! $|++;
!! ... do stuff ...
!! $|--;
!! this will alway end by resetting $| to 0, even if it
!! was originally 1
!!
!! on the other hand $|-- will always reverse the value.
!! now I will have to find a use for that ...
But so will $| = !$|, which is a lot clearer (and work for regular
variables as well).
Abigail
--
CHECK {print "another "}
INIT {print "Perl " }
END {print "Hacker\n"}
BEGIN {print "Just " }
------------------------------
Date: 09 Jul 2004 10:19:27 +0200
From: pjacklam@online.no (Peter J. Acklam)
Subject: Re: What does this do?
Message-Id: <u0whzj74.fsf@online.no>
Jeff 'japhy' Pinyan <pinyaj@rpi.edu> wrote:
> On 8 Jul 2004, Peter J. Acklam wrote:
>
> >And the latter turns on buffering also in the extremely unlikely
> >event that $| should ever be -1, in which case $|++ would turn it
> >off.
>
> Except that $| can't ever be -1 (unless you've done *| = \-1, in
> which case $|++ will throw a "Modification of read-only" error).
Darn, then someone has fooled me. What I wrote above is virtually
a citation of something I read somewhere. No big deal, though,
but now I wonder where I got it from.
Peter
--
#!/local/bin/perl5 -wp -*- mode: cperl; coding: iso-8859-1; -*-
# matlab comment stripper (strips comments from Matlab m-files)
s/^((?:(?:[])}\w.]'+|[^'%])+|'[^'\n]*(?:''[^'\n]*)*')*).*/$1/x;
------------------------------
Date: 09 Jul 2004 10:30:20 GMT
From: Villy Kruse <vek@station02.ohout.pharmapartners.nl>
Subject: Re: What does this do?
Message-Id: <slrncesstr.mtr.vek@station02.ohout.pharmapartners.nl>
On Thu, 8 Jul 2004 17:22:30 +0300,
Eugene Mikheyev <Eugene.Mikheyev@kiev.cms.com.ua> wrote:
>> $|++;
>> I see that in code but my searches have come up with nothing.
> As $| is a boolean variable, I suspect the one who wrote this thought
> incrementing is faster than assigning, i.e. when $x is 0, $x++ is faster
> than $x = 1. Maybe I am wrong, this is just an assumption.
>
If you look at it logically: increment would be more expensive as you
first have to retreive the old value before incrementing it. Assigning
1 to the variable don't need to do that. But that is nano-optimization
which usualy is a waste of programmer time.
Villy
------------------------------
Date: Fri, 9 Jul 2004 08:13:50 -0400
From: Jeff 'japhy' Pinyan <pinyaj@rpi.edu>
Subject: Re: What does this do?
Message-Id: <Pine.SGI.3.96.1040709081317.52776A-100000@vcmr-64.server.rpi.edu>
On Thu, 8 Jul 2004, gnari wrote:
>"Jeff 'japhy' Pinyan" <pinyaj@rpi.edu> wrote in message
>news:Pine.SGI.3.96.1040708181456.48121A-100000@vcmr-64.server.rpi.edu...
>>
>> $|, as defined by the internal magic supporting it, is set to 0 when given
>> a false value, and 1 when given ANY true value.
>
>in that case the $|++ does not even have the advantage
>of allowing us to 'localize' the value as in:
>
> # unknown $| state
> $|++;
> ... do stuff ...
> $|--;
>this will alway end by resetting $| to 0, even if it
>was originally 1
Luckily we have 'local' which does exactly what you want.
# unknown $| state
{
local $| = 1;
# ...
}
# $| is restored here
--
Jeff "japhy" Pinyan % How can we ever be the sold short or
RPI Acacia Brother #734 % the cheated, we who for every service
RPI Corporation Secretary % have long ago been overpaid?
http://japhy.perlmonk.org/ %
http://www.perlmonks.org/ % -- Meister Eckhart
------------------------------
Date: Fri, 09 Jul 2004 12:28:07 +0200
From: Axel Strube-Zettler <axel@strube-zettler.de>
Subject: XSLT Transformation
Message-Id: <2l7a64F93m1bU1@uni-berlin.de>
Hi all,
how can I do a XSLT transformation on a XML File (XSLT Stylesheet) -
just like Saxon does? What packages are exactly needed?
Thanks, Axel
------------------------------
Date: Fri, 09 Jul 2004 13:15:36 +0200
From: Tom Regner <regner@dievision.de>
Subject: Re: XSLT Transformation
Message-Id: <40ee7e58$0$5987$4d3ebbfe@news1.pop-hannover.net>
Axel Strube-Zettler wrote:
> how can I do a XSLT transformation on a XML File (XSLT Stylesheet) -
> just like Saxon does? What packages are exactly needed?
Jonathan Stowes XML::XSLT seems to fit, from the pod:
use XML::XSLT;
my $xslt = XML::XSLT->new ($xsl, warnings => 1);
$xslt->transform ($xmlfile);
print $xslt->toString;
CPAN:
http://search.cpan.org/~jstowe/XML-XSLT-0.48/lib/XML/XSLT.pm
kind regards,
Tom
--
Dievision GmbH | Kriegerstrasse 44 | 30161 Hannover
Telefon: (0511) 288791-0 | Telefax: (0511) 288791-99
http://www.dievision.de | mailto:regner@dievision.de
------------------------------
Date: Fri, 09 Jul 2004 13:15:44 +0200
From: "Vetle Roeim" <vetro@online.no>
Subject: Re: XSLT Transformation
Message-Id: <opsavawixf3hk3cf@quickfix.opera.com>
On Fri, 09 Jul 2004 12:28:07 +0200, Axel Strube-Zettler
<axel@strube-zettler.de> wrote:
> Hi all,
>
> how can I do a XSLT transformation on a XML File (XSLT Stylesheet) -
> just like Saxon does? What packages are exactly needed?
XML::XSLT has been suggested. XML::LibXSLT is another module that can
be used. It is a front-end to the Gnome XSLT library.
<URL: http://search.cpan.org/~msergeant/XML-LibXSLT-1.57/LibXSLT.pm >
--
It's not a bug, it's the future.
------------------------------
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 6782
***************************************
