[28297] in Perl-Users-Digest
Perl-Users Digest, Issue: 9661 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Aug 29 09:05:53 2006
Date: Tue, 29 Aug 2006 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 Tue, 29 Aug 2006 Volume: 10 Number: 9661
Today's topics:
Re: A Sort Optimization Technique: decorate-sort-dedeco <jo@durchholz.org>
How to sort a date array? <SaltyBall@Hell.com>
Re: How to sort a date array? <mritty@gmail.com>
Re: How to sort a date array? <David.Squire@no.spam.from.here.au>
Re: How to sort a date array? <bik.mido@tiscalinet.it>
Re: How to sort a date array? <tadmc@augustmail.com>
Re: integrate() anno4000@radom.zrz.tu-berlin.de
Re: integrate() <rvtol+news@isolution.nl>
Missing zeros in permutation. A perl bug or something e <StillAwake@2am>
Re: Missing zeros in permutation. A perl bug or somethi <David.Squire@no.spam.from.here.au>
Re: Missing zeros in permutation. A perl bug or somethi <David.Squire@no.spam.from.here.au>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Problem handling a Unicode file <rvtol+news@isolution.nl>
Re: Problem handling a Unicode file <lev.weissman@creo.com>
Re: Problem handling a Unicode file <rvtol+news@isolution.nl>
Re: Problem handling a Unicode file <lev.weissman@creo.com>
Re: Question about UNIVERSAL anno4000@radom.zrz.tu-berlin.de
Re: Working with Source Code to Insert Copyright Statem <bik.mido@tiscalinet.it>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 29 Aug 2006 12:50:52 +0200
From: Joachim Durchholz <jo@durchholz.org>
Subject: Re: A Sort Optimization Technique: decorate-sort-dedecorate
Message-Id: <ed1682$l41$1@online.de>
Jim Gibson schrieb:
>
> The problem addressed by what is know in Perl as the 'Schwartzian
> Transform' is that the compare operation can be an expensive one,
> regardless of the whether the comparison uses multiple keys. Since in
> comparison sorts, the compare operation will be executed N(logN) times,
> it is more efficient to pre-compute a set of keys, one for each object
> to be sorted. That need be done only N times.
Wikipedia says it's going from 2NlogN to N. If a sort is massively
dominated by the comparison, that could give a speedup of up to 100%
(approximately - dropping the logN factor is almost irrelevant, what
counts is losing that factor of 2).
Regards,
Jo
------------------------------
Date: Tue, 29 Aug 2006 19:41:51 +0800
From: SaltyBall <SaltyBall@Hell.com>
Subject: How to sort a date array?
Message-Id: <44f427f9@127.0.0.1>
Hi All,
Here we have a date array like this
@array=(2006-01-03, 2006-03-24, 2005-01-06);
when I use
sort(@array)
it did not sort correctly, the month and date was not sort, I think it
is the "-" make the sort fail, what is the correct way to sort this array?
thanks!
------------------------------
Date: 29 Aug 2006 04:52:39 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: How to sort a date array?
Message-Id: <1156852358.938752.145250@m79g2000cwm.googlegroups.com>
SaltyBall wrote:
> Here we have a date array like this
> @array=(2006-01-03, 2006-03-24, 2005-01-06);
You do understand that evaluates to:
@array = (2002, 1979, 1998);
right?
> when I use
> sort(@array)
You should get a warning telling you about a useless use of sort() in
void context. You are enabling warnings, right?
> it did not sort correctly, the month and date was not sort, I think it
> is the "-" make the sort fail, what is the correct way to sort this array?
You can start by posting a SHORT but COMPLETE script that demonstrates
the actual errors you're seeing. You would do well to read the Posting
Guidelines for this group, which contain the above and other good
advice.
my @array=('2006-01-03', '2006-03-24', '2005-01-06');
@array = sort @array;
print "@array\n";
This prints out:
2005-01-06 2006-01-03 2006-03-24
Paul Lalli
------------------------------
Date: Tue, 29 Aug 2006 12:54:53 +0100
From: David Squire <David.Squire@no.spam.from.here.au>
Subject: Re: How to sort a date array?
Message-Id: <ed19ue$lvn$1@gemini.csx.cam.ac.uk>
SaltyBall wrote:
> Hi All,
>
> Here we have a date array like this
> @array=(2006-01-03, 2006-03-24, 2005-01-06);
Do you realize that this array contains
(2002, 1979, 1998)
????
I think you mean
my @array=('2006-01-03', '2006-03-24', '2005-01-06');
> when I use
> sort(@array)
Where did you store the result of this? As you should see from the perl
documentation, sort *returns* a sorted list, it does not sort an array
in place.
> it did not sort correctly, the month and date was not sort, I think it
> is the "-" make the sort fail, what is the correct way to sort this array?
Please include small, complete script illustrating your problem -
including the output and why it is not as you expect.
Always include:
use strict;
use warnings;
at the start of you script. In this case warnings would have told you
your problem.
DS
------------------------------
Date: 29 Aug 2006 14:01:23 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: How to sort a date array?
Message-Id: <mha8f25lqhaca2nui3nrljd5soatotnke8@4ax.com>
On Tue, 29 Aug 2006 19:41:51 +0800, SaltyBall <SaltyBall@Hell.com>
wrote:
>Here we have a date array like this
>@array=(2006-01-03, 2006-03-24, 2005-01-06);
>when I use
>sort(@array)
>it did not sort correctly, the month and date was not sort, I think it
>is the "-" make the sort fail, what is the correct way to sort this array?
Which is the month? I suppose the last two digits, for otherwise it
should sort() correctly with cmp. But then just supply an explicit
sort sub. If needed, apply an "advanced" technique, e.g. a schwartzian
or GR transform, as an enhancement. What have you tried thus far? In
doubt (do a favour to yourself and) read
perldoc -f sort
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Tue, 29 Aug 2006 07:04:55 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: How to sort a date array?
Message-Id: <slrnef8bb7.ed6.tadmc@magna.augustmail.com>
anno4000@radom.zrz.tu-berlin.de <anno4000@radom.zrz.tu-berlin.de> wrote:
>> @array=(2006-01-03, 2006-03-24, 2005-01-06);
>
> That looks a bit like Perl but it isn't.
Sure it is.
Perl has a subtraction operator.
SCNR.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 29 Aug 2006 10:02:03 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: integrate()
Message-Id: <4lihkrF22nhbU1@news.dfncis.de>
Dr.Ruud <rvtol+news@isolution.nl> wrote in comp.lang.perl.misc:
> I found this interesting example on comp.lang.misc
> <news:44f24874$0$3585$ed2e19e4@ptn-nntp-reader04.plus.net>
> that I think would be nice to translate to Perl.
>
>
> > The following Mathematica code implements polynomial integration
[...]
> I assumed that somebody would have done something in this area already
> (without calling Mathematica), so I checked CPAN, but I found nothing
> for polynomial integration, so I probably just didn't look well enough,
> did I?
There's a huge family of modules Math::Symbolic::*. I'm sure there
is something...
Anno
------------------------------
Date: Tue, 29 Aug 2006 14:25:37 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: integrate()
Message-Id: <ed1j32.1d4.1@news.isolution.nl>
anno4000@radom.zrz.tu-berlin.de schreef:
> Dr.Ruud:
>> I found this interesting example on comp.lang.misc
>> <news:44f24874$0$3585$ed2e19e4@ptn-nntp-reader04.plus.net>
>> that I think would be nice to translate to Perl.
>> [...]
>> I assumed that somebody would have done something in this area
>> already (without calling Mathematica), so I checked CPAN, but I
>> found nothing for polynomial integration, so I probably just didn't
>> look well enough, did I?
>
> There's a huge family of modules Math::Symbolic::*. I'm sure there
> is something...
I searched again (like on "integration" and on "integral")
and found only
Math::Integral::Romberg - scalar numerical integration
but that is a different area. <g>
See also
http://www.tangentspace.net/cz/archives/2005/05/mathsymbolic-modules
Math::Integral is i:
http://search.cpan.org/~aqumsieh/
These have 9000 hits:
google: perl "symbolic integration"
google: perl risch integral OR integration
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Tue, 29 Aug 2006 07:42:30 -0500
From: StuPedaso <StillAwake@2am>
Subject: Missing zeros in permutation. A perl bug or something else?
Message-Id: <9ub8f25n7sd9v0gr1jrgsjs9efqfd1g8cf@4ax.com>
I found this script a few years ago, and although it works fine for
small words like rebecca, banana, alabama, oklahoma, if you try
longer, or words with lots of repeating characters, like mississippi
it will take forever. Ok, maybe not forever, but upwards of 1492
wallclock secs.
use Benchmark;
my $start_time = new Benchmark;
my @incomplete = ':rebecca';
my %complete;
while ( my $item = pop( @incomplete ) ) {
process( $item );
}
print join( "\n", sort keys %complete ), "\n";
$many = scalar keys %complete;
print "it has $many elements\n";
my $end_time = new Benchmark;
my $difference = timediff($end_time, $start_time);
print "It took ", timestr($difference), "\n";
sub process {
my $item = shift;
$item =~ /(.*):(.*)/;
if ( $2 ) {
extend( $1, $2 );
}
else {
$complete{$1} = 1;
}
}
sub extend {
my ( $done, $todo ) = @_;
my @chars = split( '', $todo );
foreach my $c ( @chars ) {
my $removed = $todo;
$removed =~ s/$c//;
push( @incomplete, "$done$c:$removed" );
}
}
The problem is, it creates the same permutation X times, where X is
the number of repeating letters you have. In rebecca there are 4.
I modified it somewhat shortly after I found it, and haven't used it
much since. It's much faster, and will do mississippi in about 2
wallclock secs. Letters seem to do ok, but recently I needed a 16 bit
binary type string with7 zeros and 9 ones so I used this script again.
Took 1 second, but with odd results.
Can anyone tell me why the permutations that should end in zero are
missing that zero?
use Benchmark;
my $start_time = new Benchmark;
%BeenHere=();
my @incomplete = ':000111';
my %complete;
while ( my $item = pop( @incomplete ) ) {
process( $item );
}
print join( "\n", sort keys %complete ), "\n";
$many = scalar keys %complete;
print "it has $many elements\n";
my $end_time = new Benchmark;
my $difference = timediff($end_time, $start_time);
print "It took ", timestr($difference), "\n";
sub process {
my $item = shift;
$item =~ /(.*):(.*)/;
if ( $2 ) {
$string="$1,$2";
$BeenHere{$string}++;
if ($BeenHere{$string}==1){
extend( $1, $2 );}
}
else {
$complete{$1} = 1;
}
}
sub extend {
my ( $done, $todo ) = @_;
my @chars = split( '', $todo );
foreach my $c ( @chars ) {
my $removed = $todo;
$removed =~ s/$c//;
push( @incomplete, "$done$c:$removed" );
}
}
Thanks
------------------------------
Date: Tue, 29 Aug 2006 13:45:59 +0100
From: David Squire <David.Squire@no.spam.from.here.au>
Subject: Re: Missing zeros in permutation. A perl bug or something else?
Message-Id: <ed1cu8$rkc$1@gemini.csx.cam.ac.uk>
StuPedaso wrote:
>
> Can anyone tell me why the permutations that should end in zero are
> missing that zero?
>
[snip]
> sub process {
> my $item = shift;
> $item =~ /(.*):(.*)/;
>
> if ( $2 ) {
I haven't done any analysis of your algorithm, but my hunch is that the
line above is the cuiprit. It will evaluate as false if $2 == '0'. Try
replacing it with
if (defined $2) {
DS
------------------------------
Date: Tue, 29 Aug 2006 13:46:53 +0100
From: David Squire <David.Squire@no.spam.from.here.au>
Subject: Re: Missing zeros in permutation. A perl bug or something else?
Message-Id: <ed1cvt$rkc$2@gemini.csx.cam.ac.uk>
David Squire wrote:
> line above is the cuiprit. It will evaluate as false if $2 == '0'. Try
s/cuiprit/culprit/
------------------------------
Date: 29 Aug 2006 07:22:21 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.6 $)
Message-Id: <44f3eb2c$0$47252$ae4e5890@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.6 $)
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://www.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 29 Aug 2006 13:40:06 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Problem handling a Unicode file
Message-Id: <ed1gce.178.1@news.isolution.nl>
MoshiachNow schreef:
> all bytes are interchanged within the words
That is the UTF16-LE order, so it would have been wrong if you would
have seen something else. Do you understand the role of the BOM (Byte
Order Mark) now?
http://en.wikipedia.org/wiki/Byte_Order_Mark
Create a fresh file in Notepad with just the word "test" in it, and do a
File/Save As..., with Encoding "Unicode", and you'll see that Windows
defaults to UTF16-LE.
You'll also find an Encoding "Unicode big-endian" there, that is
UTF16-BE. But why would you want the bytes in a different order than the
default for the platform?
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: 29 Aug 2006 05:25:25 -0700
From: "MoshiachNow" <lev.weissman@creo.com>
Subject: Re: Problem handling a Unicode file
Message-Id: <1156854325.188850.315480@b28g2000cwb.googlegroups.com>
HI,
I do run exactly this :
open my $fhi, '<:encoding(UTF-16)', $fni
or die "open '$fni', stopped $!" ;
open my $fho, '>:encoding(UTF-16)', $fno
or die "open '$fno', stopped $!" ;
and expect input and output files to be in the same order,but they are
not.
I DID try adding the following line,it did not help:
print $fho "\x{FEFF}";
------------------------------
Date: Tue, 29 Aug 2006 14:41:31 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Problem handling a Unicode file
Message-Id: <ed1k0v.1co.1@news.isolution.nl>
MoshiachNow schreef:
> I do run exactly this :
> open my $fhi, '<:encoding(UTF-16)', $fni
> or die "open '$fni', stopped $!" ;
>
>
> open my $fho, '>:encoding(UTF-16)', $fno
> or die "open '$fno', stopped $!" ;
>
> and expect input and output files to be in the same order
Why do you expect that? At input, the BOM rules. At output, the platform
rules.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: 29 Aug 2006 05:53:42 -0700
From: "MoshiachNow" <lev.weissman@creo.com>
Subject: Re: Problem handling a Unicode file
Message-Id: <1156856022.902664.170360@b28g2000cwb.googlegroups.com>
Thanks a lot.
Read the article,got the ide of the BOM.
The only thing that got me a valid output file was:
open (FILE, ">:raw:encoding(UTF16-LE)", "Araxi.reg") || die "Could not
open Araxi.reg: $!";
print FILE "\x{FEFF}";
Any other sequence will not work well.
Thanks !
------------------------------
Date: 29 Aug 2006 10:59:38 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Question about UNIVERSAL
Message-Id: <4lil0qF23ublU1@news.dfncis.de>
Ben Morrow <benmorrow@tiscali.co.uk> wrote in comp.lang.perl.misc:
>
> Quoth "Ferry Bolhar" <bol@adv.magwien.gv.at>:
> > Ben Morrow:
> >
> > >> Is this what "Regexp::DESTROY" is for?
> > >
> > > WTF??? *NO*.
> > >
> > > Regexp::DESTROY does nothing. It's defined in perl/universal.c .
> >
> > If it does nothing, why does it exist?
>
> I don't know. I suspect the memory leak you mention below has something
> to do with it, though I can't offhand come up with a situation where not
> having a DESTROY can cause leaks.
Hmmm? When memory is associated with an object not through a reference
but through other means, Perl can't trace the association. It needs
help from a destructor to avoid a memory leak. One case in point would
be inside-out objects. I would have thought the case is quite frequent.
[snip]
Anno
------------------------------
Date: 29 Aug 2006 09:40:02 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Working with Source Code to Insert Copyright Statements as a Header
Message-Id: <7ar7f2ltar5scb98j15f5ki06gsa1724i0@4ax.com>
On 28 Aug 2006 11:06:35 -0700, "Perlgirl" <sgordon@egenera.com> wrote:
>I was wondering if you could give me a hand.
Sure!
>Where could I go to find some samples of PERL code that do the
PERL?!? (But they already told you...)
>following:
>
>1. inserts a particular copyright statement
Into... WHERE?!?
>2. checks the existing copyrights and updates it to include the current
>year if it's not included
existing into... WHERE?!? Text files? Binary files? Images? Movies?
(And so on...)
>Or if the copyright has the wrong date, the script gives an error.
Ditto.
>3. It has to process particular file types (I have that info); a
^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^
How 'bout sharing that info?
>listing of files to process (I have that info too), and cannot process
>binary files (have that info too)
Ok, some more info, then. Why didn't you say so ab initio?
>Any help you can give me would be appreciated. Many thanks.
Only possible help that one can give you: since you're dealing with
text files, this is basic text processing. In particular your
copyright notices will follow some pattern. Then you have to match
that pattern and take actions accordingly. This is common routine
work. For examples of such Perl code just read some random posts and
you'll find one before too late.
OTOH all this should be straightforward to quite about anyone who has
read say the first few chapters of any introductory Perl book or
tutorial, so I recommend you doing so. Then your first attempts may
turn out not to do exactly what you want, due to misunderstanding or
inexperience: submit them to our attention and we will be happy to
provide some comment about them.
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
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 9661
***************************************
