[25726] in Perl-Users-Digest
Perl-Users Digest, Issue: 7966 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Apr 12 06:05:30 2005
Date: Tue, 12 Apr 2005 03:05:09 -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, 12 Apr 2005 Volume: 10 Number: 7966
Today's topics:
file date <alexj@floor.ch>
Re: file date (Anno Siegel)
Re: get mod_perl max memory usage <alexj@floor.ch>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Regex and detection on dhcpd.conf file (MaXX)
Re: Regex and detection on dhcpd.conf file <joe@inwap.com>
Re: Regex and detection on dhcpd.conf file (Anno Siegel)
Re: Regex and detection on dhcpd.conf file <josef.moellers@fujitsu-siemens.com>
Re: retrieving numbers. <joe@inwap.com>
Re: Simple Encryption Script (Spock)
Re: Simple Encryption Script (Anno Siegel)
Re: Simple Encryption Script (Anno Siegel)
Re: Simple Encryption Script <hackeras@gmail.com>
Re: Simple Encryption Script (Anno Siegel)
Re: Simple Encryption Script <someone@example.com>
Re: Simple Encryption Script <spamtrap@dot-app.org>
Re: Simple Encryption Script <joe@inwap.com>
Re: The Final Solution Then. <noreply@gunnar.cc>
Re: UTF-8 in regexp with 5.8.1 <groleau+news@freeshell.org>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 12 Apr 2005 10:12:39 +0200
From: Alexandre Jaquet <alexj@floor.ch>
Subject: file date
Message-Id: <d3fvtk$18c$1@news.hispeed.ch>
Hi,
I need to get the files dates on my script. I've found on the web the
following piece of code and explanation :
The -M file check returns the age in days since the file was last
changed. It includes fractional amounts, so if you want to compare days,
you need to take the ‘int’ of the returned value. The -A file check
returns the age in days since someone last looked at the file.
foreach $FileName (@ARGV) {
$FileAge = -M $FileName;
if ($FileAge < .5) {
print "\”$FileName\" is less than half a day old.\n";
} elsif ($FileAge < 1.5) {
print "\"$FileName\" is only a day old.\n";
} else {
$FileAge = int($FileAge+.5);
print "\"$FileName\" is $FileAge days old.\n";
}
}
but I didn't understand what exactly is returned by -M I want to get
"Tue Apr 12 10:11:23"
thanks in advance
Alexandre Jaquet
------------------------------
Date: 12 Apr 2005 09:36:33 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: file date
Message-Id: <d3g4r1$lh9$2@mamenchi.zrz.TU-Berlin.DE>
Alexandre Jaquet <alexj@floor.ch> wrote in comp.lang.perl.misc:
> Hi,
>
> I need to get the files dates on my script. I've found on the web the
> following piece of code and explanation :
>
> The -M file check returns the age in days since the file was last
> changed. It includes fractional amounts, so if you want to compare days,
> you need to take the ‘int’ of the returned value. The -A file check
> returns the age in days since someone last looked at the file.
>
> foreach $FileName (@ARGV) {
> $FileAge = -M $FileName;
> if ($FileAge < .5) {
> print "\”$FileName\" is less than half a day old.\n";
> } elsif ($FileAge < 1.5) {
> print "\"$FileName\" is only a day old.\n";
> } else {
> $FileAge = int($FileAge+.5);
> print "\"$FileName\" is $FileAge days old.\n";
> }
> }
>
>
> but I didn't understand what exactly is returned by -M I want to get
>
> "Tue Apr 12 10:11:23"
Then use stat():
my $time = localtime( ( stat $filename)[ 9]);
See perldoc -f stat.
Anno
------------------------------
Date: Tue, 12 Apr 2005 10:14:51 +0200
From: Alexandre Jaquet <alexj@floor.ch>
Subject: Re: get mod_perl max memory usage
Message-Id: <d3g01n$18c$2@news.hispeed.ch>
J. Gleixner a écrit :
> peter pilsl wrote:
>
>> Alexandre Jaquet wrote:
>>
>>>
>>> "how can /where can I settup mod_perl memory usage ?"
>>> "where may I can found default settings ?"
>>> "how much memory perl is allowed to use"
>>>
>>
>> Please correct me if I'm wrong but imho there is no way to setup
>> mod_perl memory usage from outside. When I wrote memleaking
>> mod_perl-scripts there was obviously no limit catching in.
>> Like in normal perl, its up to the programmer to take care how much
>> mem its programm will take.
>>
>> so the answers to your question by my experience, but not by my
>> knowledge are:
>>
>> you cant
>> there are none
>> all your system gives you
>>
>> best,
>> peter
>>
>>
>
> Correct, however to not allow memory usage to get above some limit there
> are two modules that'll help: Apache::GTopLimit and Apache::SizeLimit.
>
> There is a lot of documentation about mod_perl at: http://perl.apache.org/
ok thanks :)
------------------------------
Date: 12 Apr 2005 07:22:16 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <425b7726$0$25884$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: 12 Apr 2005 00:50:21 -0700
From: romain.daumont@int-evry.fr (MaXX)
Subject: Regex and detection on dhcpd.conf file
Message-Id: <aa422dac.0504112350.6ebc536e@posting.google.com>
Hi,
I try to extract a information (mac address) in a file dhcpd.conf. I
don't manage to detect the field "hardware ethernet" and extract the
values which follow (values hex). But, i know, for example, "toto" in
the field "host".
So, my file is composed :
host toto {
hardware ethernet 00:05:5b:22:55:96;
fixed-address 192.168.21.55;
}
host titi {
hardware ethernet 00:B0:DD:D7:FF:78;
fixed-address 192.168.21.56;
}
etc...
if you have a idea...
Thanks
------------------------------
Date: Tue, 12 Apr 2005 02:29:33 -0700
From: Joe Smith <joe@inwap.com>
Subject: Re: Regex and detection on dhcpd.conf file
Message-Id: <5vednS3FEdWcCMbfRVn-1g@comcast.com>
MaXX wrote:
> I try to extract a information (mac address) in a file dhcpd.conf.
perl -lne '/host\s+(\S+)/ and $host=$1; /ethernet\s+(\S+)/ and print
"$host $1"' dhcpd.conf
-Joe
------------------------------
Date: 12 Apr 2005 09:36:14 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Regex and detection on dhcpd.conf file
Message-Id: <d3g4qe$lh9$1@mamenchi.zrz.TU-Berlin.DE>
MaXX <romain.daumont@int-evry.fr> wrote in comp.lang.perl.misc:
> Hi,
>
> I try to extract a information (mac address) in a file dhcpd.conf. I
What information? Please be specific.
> don't manage to detect the field "hardware ethernet" and extract the
> values which follow (values hex). But, i know, for example, "toto" in
> the field "host".
>
>
> So, my file is composed :
>
> host toto {
> hardware ethernet 00:05:5b:22:55:96;
> fixed-address 192.168.21.55;
> }
> host titi {
> hardware ethernet 00:B0:DD:D7:FF:78;
> fixed-address 192.168.21.56;
> }
If you give example data you should always describe the variability
in the data. The details of a solution depend heavily on that. Just
a few questions your example raises:
- Are there always four lines to the record?
- Is the sequence always "hardware ethernet ..." followed by "fixed-address"?
- Is "host" always at the beginning of a line?
- Are the "middle lines" always indented by 8 blanks? Could there be tabs?
- Are the words on a line always separated by exactly one blank? Could
there be tabs?
...and so on.
Making some assumptions about the answers, here is one solution (replace
"DATA" with a filehandle to your dhcpd.conf):
my $host = 'toto';
$/ = "}\n"; # should be localized in a real program
while ( <DATA> ) {
if ( /^host $host/ ) {
my ( $mac_addr) = /hardware ethernet ([0-9a-f:]+)/i;
print "$host: $mac_addr\n";
}
}
Anno
------------------------------
Date: Tue, 12 Apr 2005 11:41:47 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: Regex and detection on dhcpd.conf file
Message-Id: <d3g5ak$eu4$1@nntp.fujitsu-siemens.com>
MaXX wrote:
> Hi,
>=20
> I try to extract a information (mac address) in a file dhcpd.conf. I
> don't manage to detect the field "hardware ethernet" and extract the
> values which follow (values hex). But, i know, for example, "toto" in
> the field "host".
>=20
>=20
> So, my file is composed : =20
>=20
> host toto {
> hardware ethernet 00:05:5b:22:55:96;
> fixed-address 192.168.21.55;
> }
> host titi {
> hardware ethernet 00:B0:DD:D7:FF:78;
> fixed-address 192.168.21.56;
> }
> etc...
>=20
> if you have a idea...
Read the file line-by-line looking for the host line.
If you find the host line, start looking for the hardware ethernet line.
my $hostfound =3D 0;
my $host =3D 'toto';
while (<DHCPD_CONF>) {
if (!$hostfound) {
if (/^\s*host\s+$host\b/) {
$hostfound =3D 1;
}
next;
} elsif (/^\s+hardware\s+ethernet\s+(\S+)\s*;/) {
print "$1\n";
last;
} elsif (/^\s*}/) {
last;
}
}
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: Tue, 12 Apr 2005 02:38:06 -0700
From: Joe Smith <joe@inwap.com>
Subject: Re: retrieving numbers.
Message-Id: <Geidnd_OFO2eCsbfRVn-2g@comcast.com>
Chris Mattern wrote:
> if ($input_string =~ /^([0-9]*) /) { $my_number = $1; }
Any particular reason why you chose [0-9] instead of \d ?
The repeat character + would be more suitable than * in this case.
if ($input_string =~ /^(\d+)/ { $my_number = $1; }
-Joe
------------------------------
Date: 12 Apr 2005 00:46:29 -0700
From: hackeras@gmail.com (Spock)
Subject: Re: Simple Encryption Script
Message-Id: <edb4631.0504112346.3d8878c@posting.google.com>
> You might want to actually, y'know, try it before you state it doesn't
> work. Or you could read the documentation for foreach.
But i did, because you are adding chars it didnt work.
------------------------------
Date: 12 Apr 2005 08:45:23 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Simple Encryption Script
Message-Id: <d3g1r3$jg1$1@mamenchi.zrz.TU-Berlin.DE>
John W. Krahn <krahnj@telus.net> wrote in comp.lang.perl.misc:
> Anno Siegel wrote:
> >
> > It works now, but it is still somewhat roundabout. You can change
> > the array elements one by one in the foreach loop, there is no need to
> > use an index ($i) to access them:
> >
> > foreach ( @letters ) {
> > $_ = 1 + chr ord $_;
> > }
>
> You are adding one to the character returned from chr()?
Oops. Should be "chr 1 + ord $_", of course. Thanks for pointing it
out.
Anno
------------------------------
Date: 12 Apr 2005 08:53:10 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Simple Encryption Script
Message-Id: <d3g29m$jg1$2@mamenchi.zrz.TU-Berlin.DE>
Chris Mattern <matternc@comcast.net> wrote in comp.lang.perl.misc:
> Nikos wrote:
>
> > anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) wrote in news:d3djrj$3iq$1
> > @mamenchi.zrz.TU-Berlin.DE:
> >
> >> foreach ( @letters ) {
> >> $_ = 1 + chr ord $_;
> >> }
> >
> > Yes but this wont change the value of its element. i mean the new value of
> > every element will not be stored it will just change.
> >
> You might want to actually, y'know, try it before you state it doesn't
> work. Or you could read the documentation for foreach.
Well, in fact it doesn't work as intended, as John W. Krahn pointed out
("1 + chr ord $_" should be "chr 1 + ord $_"). But that's a different
problem than the non-existent one Nikos anticipated.
Anno
------------------------------
Date: Tue, 12 Apr 2005 12:12:27 +0300
From: Nikos <hackeras@gmail.com>
Subject: Re: Simple Encryption Script
Message-Id: <d3g3dp$bpd$2@nic.grnet.gr>
Anno Siegel wrote:
> Oops. Should be "chr 1 + ord $_", of course. Thanks for pointing it
> out.
Yes. Guys i noticed that you dont use parenthessis in functions. why?
isnt it better to see and read a function containing parenthesis?
------------------------------
Date: 12 Apr 2005 09:42:11 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Simple Encryption Script
Message-Id: <d3g55j$lh9$3@mamenchi.zrz.TU-Berlin.DE>
Nikos <hackeras@gmail.com> wrote in comp.lang.perl.misc:
> Anno Siegel wrote:
>
> > Oops. Should be "chr 1 + ord $_", of course. Thanks for pointing it
> > out.
>
> Yes. Guys i noticed that you dont use parenthessis in functions. why?
> isnt it better to see and read a function containing parenthesis?
Shrug. It's a matter of style. Most people seem to prefer putting
parentheses only where they are needed. Sometimes a pair of not-strictly-
necessary parens can make things clearer. Always writing all parens
clutters the code.
Anno
------------------------------
Date: Tue, 12 Apr 2005 09:51:41 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Simple Encryption Script
Message-Id: <NSM6e.21027$yV3.15045@clgrps12>
Nikos wrote:
> Anno Siegel wrote:
>
>> Oops. Should be "chr 1 + ord $_", of course. Thanks for pointing it
>> out.
>
> Yes. Guys i noticed that you dont use parenthessis in functions. why?
> isnt it better to see and read a function containing parenthesis?
That is because we are using operators which don't require parentheses instead
of functions which do. (The operators 'chr', '+' and 'ord' to be specific.)
perldoc perlop
John
--
use Perl;
program
fulfillment
------------------------------
Date: Tue, 12 Apr 2005 05:58:08 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: Simple Encryption Script
Message-Id: <o-SdnYmwTLksBsbfRVn-3A@adelphia.com>
John W. Krahn wrote:
> That is because we are using operators which don't require parentheses
> instead of functions which do. (The operators 'chr', '+' and 'ord' to be
> specific.)
Um... Did I miss something? chr() and ord() are both listed in perlfunc.
And functions in general often don't require parentheses.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Tue, 12 Apr 2005 03:01:27 -0700
From: Joe Smith <joe@inwap.com>
Subject: Re: Simple Encryption Script
Message-Id: <eM6dnUz-tcrkAcbfRVn-3g@comcast.com>
Nikos wrote:
> $i=0;
> foreach (@letters) {
> $letters[$i++] = chr( ord($_) + 1 );
> }
Since you are using $letters[$i] in the loop, you shouldn't be
using foreach(@letters){}.
When working with indexes into an array (as opposed to the elements
in the array), start at 0 and end at the highest array index.
foreach my $i (0 .. $#letters) {
$letters[$i] = chr(ord($letters[$i])+1);
}
-Joe
------------------------------
Date: Tue, 12 Apr 2005 10:17:19 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: The Final Solution Then.
Message-Id: <3c1ef2F6ita1nU1@individual.net>
Tad McClellan wrote:
> Corne van Tonder <cvt@blueyonder.co.uk> wrote:
>>
>> ($ent_id, $ent_path) = split();
>
>> Things to note.....
>> 1) By default split() uses $_
>
> No programmer needs to make note of that, because they would
> have read the documentation for the function they are using,
> which says pretty clearly what split defaults to using.
Please, Tad...
To Corne: I for one think you made a summary of this thread worthy of
imitation. Thanks!
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Mon, 11 Apr 2005 23:41:40 -0500
From: Wes Groleau <groleau+news@freeshell.org>
Subject: Re: UTF-8 in regexp with 5.8.1
Message-Id: <d3fjgi$309$1@domitilla.aioe.org>
Alan J. Flavell wrote:
> On Sun, 10 Apr 2005, Wes Groleau wrote:
>>I have a file containing thousands of Spanish words, encoded AFAIK)
>>in UTF-8.
>
> Well, your whole report stands or falls by that "AFAIK", so it might
Well, I told my editor to save it as UTF-8, and I think it works.
(When I save web pages that way, and specify UTF-8 in a META tag,
Spanish, French, Polish, and Japanese characters are correctly
rendered by most browsers.)
>>I also have a perl script in UTF-8,
>
> Noted, although I don't see any compelling reason to code the script
> itself in utf-8. Sure, you /can/ do, but it seems to me to be a
> potential additional complication that one could do well to avoid
Well, in this case, I am trying to regexp a non-ASCII character.
Since I am an easily-distracted (A.D.D.) type, and I work with
several different character sets, I am attempting to standardize
on UTF-8 rather than constantly be debugging places where I forgot
to make a switch. :-)
>>#!/usr/bin/perl -w -CSD
>>#
>># NOTE: The extra space in the bang line is mandatory (bug in perl 5.8)
>
> Do you have a cite on that? My knowledge of this area is admittedly
> somewhat limited, but I hadn't met this before.
Oh, I reported that a while back. If I take the space out
on Mac OS X, I get frequent segment violations. If I remove
the space on NetBSD/Alpha, I get consistent nasty-grams about
the wrong method of invoking the debugger.
> I've successfully processed utf-8 and utf-16 data without the use of
> the -C flag(s), by using explicit binmode() on the relevant files.
I tried a couple of things with binmode that also didn't work,
but I don't remember exactly what happened.
> If you could at least get one working variant of your script, you
> could then at least move forward from there.
>
> Sorry, this is a bit inconclusive, as yet.
Well, a post in another thread made me try removing the
"use utf8" and it worked. So, I really think this is
a bug:
- A regexp containing a non-ASCII character in
correct UTF-8 encoding works.
- Add "use utf8" and it silently stops working.
- Add 'use encoding "utf8"' and you get chewed out
for having invalid UTF-8, in a message that bitches
about the presence of bytes that don't exist.
I'll send it in .....
--
Wes Groleau
He that is good for making excuses, is seldom good for anything else.
-- Benjamin Franklin
------------------------------
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 7966
***************************************
