[26213] in Perl-Users-Digest
Perl-Users Digest, Issue: 8399 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Sep 9 06:05:19 2005
Date: Fri, 9 Sep 2005 03: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 Sep 2005 Volume: 10 Number: 8399
Today's topics:
Complex data structures and variable scope <news@lawshouse.org>
Echoing fatal errors in Unix vs. Windows <uctraing@ultranet.com>
Re: Echoing fatal errors in Unix vs. Windows <""alexjaquet\"@[no spam]msn.com">
Re: Echoing fatal errors in Unix vs. Windows <sbryce@scottbryce.com>
Re: Echoing fatal errors in Unix vs. Windows <""alexjaquet\"@[no spam]msn.com">
Re: Echoing fatal errors in Unix vs. Windows <sbryce@scottbryce.com>
Re: Echoing fatal errors in Unix vs. Windows <tintin@invalid.invalid>
Re: getting font info? <ngoc@yahoo.com>
Re: My Net::eBay PERL module now recommended by eBay it <sdn.girths00869@zoemail.net>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
print chinese char <""alexjaquet\"@[no spam]msn.com">
Replace substring "_.modem_" with modem price from $pri <martina@martina.yu>
Re: Replace substring "_.modem_" with modem price from (Anno Siegel)
script attack <""alexjaquet\"@[no spam]msn.com">
Re: script attack xhoster@gmail.com
Re: use hash in a list <joe@inwap.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 09 Sep 2005 09:29:35 +0100
From: Henry Law <news@lawshouse.org>
Subject: Complex data structures and variable scope
Message-Id: <26h2i1dk2hp5eu46lhblp8sllhuebjhjj2@4ax.com>
I wonder if someone can help me with working out where to define my
variables so as to give the desired result here...
Personnel data is to be read from a file. Attributes for each
employee are presented as name/value pairs; some pairs occur once
only, but each person can have more than one qualification. The data
is to be accumulated in a hash, keyed by the person's name; each
person's hash contains their attributes, plus an reference to an array
containing their qualifications. This enables me (using other
programming not relevant here) to look up any employee by name and
present their attributes and qualifications.
Here's a runnable program which shows where I've got to. It gives the
wrong results and I'm trying to work out how to fix it.
--------------- <start of example> -----------------
#! C:\Perl\bin\perl.exe
use strict;
use warnings;
use Data::Dumper;
my %people;
my %attrs;
my @quals;
while (my $rec = <DATA>) {
#my %attrs;
#my @quals;
chomp $rec;
if ($rec) {
my ($name,$value) = split /:/, $rec;
if ($name eq "qual") {
push @quals,$value;
next;
}
$attrs{$name} = $value;
} else { # End of person
$attrs{quals} = \@quals;
$people{$attrs{name}} = \%attrs;
#undef %attrs;
#undef @quals;
}
}
print Dumper(%people);
__END__
name:alice
occupation:analyst
born:aberdeen
qual:a1
qual:a2
name:bob
occupation:baker
status:broken
qual:b1
qual:b2
---------------- <end of example> ------------------
This results in
$VAR1 = 'alice';
$VAR2 = {
'quals' => [
'a1',
'a2',
'b1',
'b2'
],
'status' => 'broken',
'name' => 'bob',
'born' => 'aberdeen',
'occupation' => 'baker'
};
I can see what's wrong: %attrs and @quals have scope outside the
file-read loop, so when the program gets to Bob's records they either
add to or replace Alice's. But I can't define them inside the read
loop because they then disappear and reappear with each record (you
can see where I tried this in the comments). I've also tried
undef-ing the arrays at the end of each person (also as shown),
without getting the desired result.
Can someone make some suggestions? I'm prepared to structure the
whole program differently but the data format is a given.
--
Henry Law <>< Manchester, England
------------------------------
Date: Fri, 09 Sep 2005 05:24:14 GMT
From: Bob <uctraing@ultranet.com>
Subject: Echoing fatal errors in Unix vs. Windows
Message-Id: <0o62i19ep63pc9jfruj5gkq0vb09dp2k2h@4ax.com>
Ok... I'm a windows guy and woefully weak in Unix skills.
WHen I run a script on my windows IIS server, and Perl script
errors (e.g. coding problems) get echoed back to the browser.
When I load the same programs on my ISP's Linux server, I
get "Internal Server Error, see log". Unfortunately, I don't
seem to have access to that log file in my virtual environment.
I assume this has something to do with std err vs. std out and
where that output goes - but that's about the limit of my Unix
knowledge. How can I redirect the error output to dump back to
the browser ?
Thanks,
------------------------------
Date: Fri, 09 Sep 2005 07:33:27 +0200
From: Alexandre Jaquet <""alexjaquet\"@[no spam]msn.com">
Subject: Re: Echoing fatal errors in Unix vs. Windows
Message-Id: <S89Ue.31772$hV3.13505@nntpserver.swip.net>
Bob a écrit :
> Ok... I'm a windows guy and woefully weak in Unix skills.
>
> WHen I run a script on my windows IIS server, and Perl script
> errors (e.g. coding problems) get echoed back to the browser.
> When I load the same programs on my ISP's Linux server, I
> get "Internal Server Error, see log". Unfortunately, I don't
> seem to have access to that log file in my virtual environment.
>
> I assume this has something to do with std err vs. std out and
> where that output goes - but that's about the limit of my Unix
> knowledge. How can I redirect the error output to dump back to
> the browser ?
>
> Thanks,
Hi use
print "Content-type: image/html\n\n";
print "$var";
------------------------------
Date: Thu, 08 Sep 2005 23:34:30 -0600
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: Echoing fatal errors in Unix vs. Windows
Message-Id: <YKGdnZ2dnZ2LlTb9nZ2dnXiDvN6dnZ2dRVn-zp2dnZ0@comcast.com>
Bob wrote:
> How can I redirect the error output to dump back to the browser ?
http://search.cpan.org/~lds/CGI.pm-3.11/CGI/Carp.pm
http://search.cpan.org/~lds/CGI.pm-3.11/CGI/Carp.pm#MAKING_PERL_ERRORS_APPEAR_IN_THE_BROWSER_WINDOW
------------------------------
Date: Fri, 09 Sep 2005 07:36:35 +0200
From: Alexandre Jaquet <""alexjaquet\"@[no spam]msn.com">
Subject: Re: Echoing fatal errors in Unix vs. Windows
Message-Id: <Ob9Ue.31774$hV3.13239@nntpserver.swip.net>
Scott Bryce a écrit :
> Bob wrote:
>
>> How can I redirect the error output to dump back to the browser ?
>
>
> http://search.cpan.org/~lds/CGI.pm-3.11/CGI/Carp.pm
> http://search.cpan.org/~lds/CGI.pm-3.11/CGI/Carp.pm#MAKING_PERL_ERRORS_APPEAR_IN_THE_BROWSER_WINDOW
>
It will be better to use
print "Content-type: text/html\n\n";
print "$var";
------------------------------
Date: Thu, 08 Sep 2005 23:59:18 -0600
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: Echoing fatal errors in Unix vs. Windows
Message-Id: <Fs6dnZxtDeUuubzeRVn-iA@comcast.com>
Alexandre Jaquet > wrote:
> It will be better to use
>
> print "Content-type: text/html\n\n";
> print "$var";
How would this cause fatal errors to be echoed in the browser?
------------------------------
Date: Fri, 9 Sep 2005 20:52:07 +1200
From: "Tintin" <tintin@invalid.invalid>
Subject: Re: Echoing fatal errors in Unix vs. Windows
Message-Id: <X2cUe.10105$iM2.929756@news.xtra.co.nz>
"Alexandre Jaquet" <""alexjaquet\"@[no spam]msn.com"> wrote in message
news:Ob9Ue.31774$hV3.13239@nntpserver.swip.net...
> Scott Bryce a écrit :
>> Bob wrote:
>>
>>> How can I redirect the error output to dump back to the browser ?
>>
>>
>> http://search.cpan.org/~lds/CGI.pm-3.11/CGI/Carp.pm
>> http://search.cpan.org/~lds/CGI.pm-3.11/CGI/Carp.pm#MAKING_PERL_ERRORS_APPEAR_IN_THE_BROWSER_WINDOW
>
> It will be better to use
>
> print "Content-type: text/html\n\n";
> print "$var";
You have a bizzare definition of "better".
See what happens when you try running the following 2 Perl CGI scripts and
then tell me which is better.
#!/usr/bin/perl
use strict;
use CGI;
my $q = new CGI;
print $q->header;
print $q->h1("Hello World");
stuffup=foobar;
#!/usr/bin/perl
use strict;
use CGI;
use CGI::Carp qw(fatalsToBrowser);
my $q = new CGI;
print $q->header;
print $q->h1("Hello World");
stuffup=foobar;
------------------------------
Date: Fri, 09 Sep 2005 07:27:58 +0200
From: ngoc <ngoc@yahoo.com>
Subject: Re: getting font info?
Message-Id: <43212a54$1@news.broadpark.no>
Jim Gibson wrote:
>
> Under most circumstances, Perl writes ASCII (or UTF8) characters to
> standard output, a file, or some device. How these characters are
> rendered depends upon the output device, not Perl. The font of
> characters displayed on your screen is determined by the window
> application (e.g. xterm), the window manager, and the operating system.
> You have specified none of these.
Yes,
my $default_font = $mw->X11Font();
$list->configure(-font => $default_font);
does not work.
>
> Posted Via Usenet.com Premium Usenet Newsgroup Services
> ----------------------------------------------------------
> ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
> ----------------------------------------------------------
> http://www.usenet.com
------------------------------
Date: Thu, 08 Sep 2005 23:14:39 -0500
From: "Eric J. Roode" <sdn.girths00869@zoemail.net>
Subject: Re: My Net::eBay PERL module now recommended by eBay itself
Message-Id: <Xns96CC2C8E95F4sdn.comcast@216.196.97.136>
Ignoramus12789 <ignoramus12789@NOSPAM.12789.invalid> wrote in
news:MBPRe.60261$Jz4.50444@fe50.usenetserver.com:
> The Perl::eBay module that I wrote a few days ago, is now recommended
> by ebay:
>
> http://developer.ebay.com/php/
Hey, that's pretty cool. Good for you.
--
Eric
`$=`;$_=\%!;($_)=/(.)/;$==++$|;($.,$/,$,,$\,$",$;,$^,$#,$~,$*,$:,@%)=(
$!=~/(.)(.).(.)(.)(.)(.)..(.)(.)(.)..(.)......(.)/,$"),$=++;$.++;$.++;
$_++;$_++;($_,$\,$,)=($~.$"."$;$/$%[$?]$_$\$,$:$%[$?]",$"&$~,$#,);$,++
;$,++;$^|=$";`$_$\$,$/$:$;$~$*$%[$?]$.$~$*${#}$%[$?]$;$\$"$^$~$*.>&$=`
------------------------------
Date: 09 Sep 2005 07:22:25 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <43213831$0$4865$8b463f8a@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.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, 09 Sep 2005 09:05:26 +0200
From: Alexandre Jaquet <""alexjaquet\"@[no spam]msn.com">
Subject: print chinese char
Message-Id: <5vaUe.31786$hV3.13568@nntpserver.swip.net>
Hi,
Does anyone know how can I print chinese content.
I save a conf file who contain chinese translation of my label but when
I print out the content I got ????? and not 新用户
In my http.conf file I got :
AddCharset ISO-8859-1 .iso8859-1 .latin1
AddCharset ISO-8859-2 .iso8859-2 .latin2 .cen
AddCharset ISO-8859-3 .iso8859-3 .latin3
AddCharset ISO-8859-4 .iso8859-4 .latin4
AddCharset ISO-8859-5 .iso8859-5 .latin5 .cyr .iso-ru
AddCharset ISO-8859-6 .iso8859-6 .latin6 .arb
AddCharset ISO-8859-7 .iso8859-7 .latin7 .grk
AddCharset ISO-8859-8 .iso8859-8 .latin8 .heb
AddCharset ISO-8859-9 .iso8859-9 .latin9 .trk
AddCharset ISO-2022-JP .iso2022-jp .jis
AddCharset ISO-2022-KR .iso2022-kr .kis
AddCharset ISO-2022-CN .iso2022-cn .cis
AddCharset Big5 .Big5 .big5
AddCharset WINDOWS-1251 .cp-1251 .win-1251
AddCharset CP866 .cp866
AddCharset KOI8-r .koi8-r .koi8-ru
AddCharset KOI8-ru .koi8-uk .ua
AddCharset ISO-10646-UCS-2 .ucs2
AddCharset ISO-10646-UCS-4 .ucs4
AddCharset UTF-8 .utf8
Thanks
------------------------------
Date: Fri, 9 Sep 2005 10:21:00 +0200
From: "Martina" <martina@martina.yu>
Subject: Replace substring "_.modem_" with modem price from $price ?
Message-Id: <dfrglb$4um$1@ss405.t-com.hr>
How to replace (change) some pattern in array with value of variable.
Replace substring "_.modem_" with modem price from $price
----------------------
@fileList=("Price for new modem is: _modem_?.", "Modem is price is:
_modem_?.");
$price=10;
foreach $red(@fileList){@rast = split ("_modem_",$red);
if ($#rast > 0) {
print "$rast[0]$price$rast[1]\n";
}
}
--------------
Any better way to solve this problem?
Tnx.
------------------------------
Date: 9 Sep 2005 09:01:39 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Replace substring "_.modem_" with modem price from $price ?
Message-Id: <dfrj1j$dpn$1@mamenchi.zrz.TU-Berlin.DE>
Martina <martina@martina.yu> wrote in comp.lang.perl.misc:
> How to replace (change) some pattern in array with value of variable.
> Replace substring "_.modem_" with modem price from $price
Please use warnings and strict in your code. In consequence, you'll
have to declare your variables. Also your code would profit from
some white space.
Your code doesn't change anything, it only prints the changed strings.
> ----------------------
> @fileList=("Price for new modem is: _modem_?.", "Modem is price is:
> _modem_?.");
Is @fileList an appropriate name? The elements don't look like plausible
file names.
> $price=10;
>
> foreach $red(@fileList){@rast = split ("_modem_",$red);
The first argument of split() is a regex, it should be written as such:
... split /_modem_/, $red;
> if ($#rast > 0) {
> print "$rast[0]$price$rast[1]\n";
Since you already have the pieces in a list you can put them together
with join();
print join( $price, @rast), "\n";
> }
> }
> --------------
>
> Any better way to solve this problem?
If your problem description is correct, you don't have a solution yet.
The normal way in Perl to change parts of a string is a substitution
s///. This changes the elements of @fileList according to your
description:
my @fileList = (
'Price for new modem is: _modem_?.',
'Modem is price is: _modem_?.',
);
my $price = 10;
s/_modem_/$price/ for @fileList;
print "$_\n" for @fileList;
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
------------------------------
Date: Fri, 09 Sep 2005 07:31:54 +0200
From: Alexandre Jaquet <""alexjaquet\"@[no spam]msn.com">
Subject: script attack
Message-Id: <q79Ue.31771$hV3.13505@nntpserver.swip.net>
Hi
I found an very interesting article at
http://groups.google.com/group/Software-Quality-Process-Group/browse_thread/thread/f99c70fcc83de076/9b4d0ce0070fa2a4?lnk=st&q=perl+sql+injection&rnum=8&hl=en#9b4d0ce0070fa2a4
and would like to use the regex described
but how to use it if I have for exemple :
local our $article = $query->param ('search_name');
if ($article =~ /((\%3D)|(=))[^\n]*((\%27)|(\')|(\-\-)|(\%3B)|(;))/i) {
$article = '*';
}
doesn't work
any help thanks
------------------------------
Date: 09 Sep 2005 06:48:06 GMT
From: xhoster@gmail.com
Subject: Re: script attack
Message-Id: <20050909024806.281$xS@newsreader.com>
Alexandre Jaquet <""alexjaquet\"@[no spam]msn.com"> wrote:
...
> doesn't work
Worst Description Ever.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: Fri, 09 Sep 2005 01:23:01 -0700
From: Joe Smith <joe@inwap.com>
Subject: Re: use hash in a list
Message-Id: <kfydna9zgLv227zeRVn-qw@comcast.com>
a wrote:
> Peter NY English
> Jane ON French
> Charles NY English
my %employee_by_language;
while (<>) {
my($name_co,$lang) =~ /(.* \w\w) (.*)/;
push @{$employee_by_language{$lang}},$name_co;
}
------------------------------
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 8399
***************************************
