[28240] in Perl-Users-Digest
Perl-Users Digest, Issue: 9604 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Aug 14 18:15:27 2006
Date: Mon, 14 Aug 2006 15:15:18 -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 Mon, 14 Aug 2006 Volume: 10 Number: 9604
Today's topics:
Re: match 2D patterns with perl <rmuschall@tecont.de>
Multiposting Notification Bot [Was Re: LWP::UserAgent q axel@white-eagle.invalid.uk
Re: Parsing text to array <tzz@lifelogs.com>
Re: Parsing text to array <mritty@gmail.com>
Re: Parsing text to array <tzz@lifelogs.com>
Re: Parsing text to array anno4000@radom.zrz.tu-berlin.de
Re: PERL ---> Move email from Inbox folder to another o <benmorrow@tiscali.co.uk>
Re: Publicly flog David Filmer for writing multi-post f usenet@DavidFilmer.com
Re: Publicly flog David Filmer for writing multi-post f usenet@DavidFilmer.com
Re: regex and utf8 characters (german umlauts) <tzz@lifelogs.com>
Re: regex and utf8 characters (german umlauts) <benmorrow@tiscali.co.uk>
Re: regex and utf8 characters (german umlauts) <tzz@lifelogs.com>
Re: UK Recruitment for Junior Perl Developer <sigzero@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 14 Aug 2006 18:22:46 +0200
From: Ralf Muschall <rmuschall@tecont.de>
Subject: Re: match 2D patterns with perl
Message-Id: <njk6r3-o93.ln1@prcm.tecont.de>
FangQ wrote:
...
> Here is an example, the original glyph looks like
> which contains a square-like pattern. I want to change it to
No - it contains an 'A'-like shape. Is this intentional
or a typo?
> 1. can I do this maching and replacement easily in perl? can you give
> me a short example?
> 2. if not, what is the best tool for this purpose? (I can always write
> loops and exhaust all possible combinations with C or other programming
> languages, but I think they are not elegant.)
You might try this:
1. replace 011..110 by 021..120
2. transpose the array (i.e. swap rows and columns)
3. replace 021..120 by 001..100
4. transpose again
This probably breaks on more complicated patterns.
Ralf
------------------------------
Date: Mon, 14 Aug 2006 20:37:09 GMT
From: axel@white-eagle.invalid.uk
Subject: Multiposting Notification Bot [Was Re: LWP::UserAgent question--MULTIPOSTED]
Message-Id: <V95Eg.13755$lv.1104@fed1read12>
usenet.cop@3955291010.com wrote:
> **********************************************************************
> ********** PLEASE DO NOT RESPOND TO THIS THREAD ***********
> **********************************************************************
> This message has been multiposted as indicated by these message IDs:
> <JoPDg.386093$Mn5.194189@pd7tw3no>
> <GbPDg.382930$iF6.158066@pd7tw2no>
It might be more informative if the actual groups to which the messages
were multiposted were named.
[ Excessive verbage snipped ]
> # NAQ (the Never Asked Questions - TEMPORARY SECTION) #
> # Q-What ruleset defines a multipost? A--Two MD5 digests are #
> # calculated (one forwards, one backwards) on the message body #
> # and stored in a small database. If a new post (new message ID) #
> # matches these digests, it's a multipost. Author and subject #
> # lines are not taken into account. Reply messages are ignored. #
> # Q-Are crossposts flagged? A--No. A message must have an identical #
> # body but a unique message ID to be flagged. A crosspost which is #
Presumably this means that a single extra space or line distinguishing
two messages (easy enough to do even if not deliberately using
cut-and-paste) would not cause them to be flagged as multiposted. So the
bot would be only partically effective.
> # Q-What groups are scanned? A-The main Perl Groups in Google Groups,#
> # namely: comp.lang.perl.misc, perl.beginners, perl.dbi.users, #
> # comp.lang.perl.modules , perl.beginners.cgi, and alt.perl #
I can see a problem here... perl.beginners exists as a mailing list
which is gatewayed to Usenet. Someone might mail to the list and also
post to a Usenet group, not realising that perl.beginners also appears
on Usenet, although possibly not on his server.
Axel
------------------------------
Date: Mon, 14 Aug 2006 11:39:37 -0400
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Parsing text to array
Message-Id: <g69psf39vie.fsf@CN1374059D0130.kendall.corp.akamai.com>
On 11 Aug 2006, benmorrow@tiscali.co.uk wrote:
> Quoth Ala Qumsieh <notvalid@email.com>:
>> as compared with Anno's map() solution.
>
> Which is entirely standard Perl. Not understanding map is nearly as bad
> as not understanding hashes: it is a fundamental part of Perl.
I disagree. You can write very good Perl code without using map(),
for very complicated programs and modules. It's next to impossible to
write good Perl code without hashes (except in very limited situations
or short programs). I would say grep() is much more important than
map() actually, and for grep() the above statement holds true.
Ted
------------------------------
Date: 14 Aug 2006 11:35:12 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: Parsing text to array
Message-Id: <1155580512.131899.163760@75g2000cwc.googlegroups.com>
Ted Zlatanov wrote:
> On 11 Aug 2006, benmorrow@tiscali.co.uk wrote:
>
> > Quoth Ala Qumsieh <notvalid@email.com>:
> >> as compared with Anno's map() solution.
> >
> > Which is entirely standard Perl. Not understanding map is nearly as bad
> > as not understanding hashes: it is a fundamental part of Perl.
>
> I disagree. You can write very good Perl code without using map(),
> for very complicated programs and modules. It's next to impossible to
> write good Perl code without hashes (except in very limited situations
> or short programs). I would say grep() is much more important than
> map() actually, and for grep() the above statement holds true.
map can be written using a for loop and a push
grep can be written using a for loop, an if statement, and a push
I do not believe either is more complicated, important, or fundamental
than the other.
Paul Lalli
------------------------------
Date: Mon, 14 Aug 2006 15:22:37 -0400
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Parsing text to array
Message-Id: <g69zme76s1u.fsf@CN1374059D0130.kendall.corp.akamai.com>
On 14 Aug 2006, mritty@gmail.com wrote:
Ted Zlatanov wrote: > On 11 Aug 2006, benmorrow@tiscali.co.uk wrote: >
>>> Quoth Ala Qumsieh <notvalid@email.com>:
>>>> as compared with Anno's map() solution.
>>>
>>> Which is entirely standard Perl. Not understanding map is nearly as bad
>>> as not understanding hashes: it is a fundamental part of Perl.
>>
>> I disagree. You can write very good Perl code without using map(),
>> for very complicated programs and modules. It's next to impossible to
>> write good Perl code without hashes (except in very limited situations
>> or short programs). I would say grep() is much more important than
>> map() actually, and for grep() the above statement holds true.
>
> map can be written using a for loop and a push
> grep can be written using a for loop, an if statement, and a push
We're not arguing about basics. I also didn't mention the speed
penalty of map()/grep(), assuming everyone knows about it, or the
decrease in legibility the use of map() incurs quite often.
> I do not believe either is more complicated, important, or fundamental
> than the other.
OK.
Ted
------------------------------
Date: 14 Aug 2006 20:22:53 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Parsing text to array
Message-Id: <4kc4ctFaim0uU1@news.dfncis.de>
Paul Lalli <mritty@gmail.com> wrote in comp.lang.perl.misc:
> Ted Zlatanov wrote:
> > On 11 Aug 2006, benmorrow@tiscali.co.uk wrote:
> >
> > > Quoth Ala Qumsieh <notvalid@email.com>:
> > >> as compared with Anno's map() solution.
> > >
> > > Which is entirely standard Perl. Not understanding map is nearly as bad
> > > as not understanding hashes: it is a fundamental part of Perl.
> >
> > I disagree. You can write very good Perl code without using map(),
> > for very complicated programs and modules. It's next to impossible to
> > write good Perl code without hashes (except in very limited situations
> > or short programs). I would say grep() is much more important than
> > map() actually, and for grep() the above statement holds true.
>
> map can be written using a for loop and a push
> grep can be written using a for loop, an if statement, and a push
>
> I do not believe either is more complicated, important, or fundamental
> than the other.
I also think that deciding which of map() and grep() is more fundamental
is besides the point. They are builtins that make new lists of given
lists. sort() is a third one, and splice() could also be mentioned.
Other list-transformers, though not named functions, are hash-, array-
and list slices. Their common message is that arrays and/or lists can
be treated as the unit of computation instead of the scalars that make
them up.
Where applicable this simplifies the thought process and along with it
the program. The simplification is fundamental and usually results in
tight code, meaning a lot of stuff happens in just a few lines.
It also means that if you have understood a few lines, you have understood
a lot about the program. Tight code, in this sense, *will* take a few
extra reading skills and may still take more time to read than that many
lines of more pedestrian broader code. Some of the required techniques,
like reading parts of the code back-to-front, are admittedly awkward.
This is offset by the fundamental simplification that comes with working
with aggregates as units. Since the unit of computation is more complex
(hiding details), the thought process is simplified.
That is why I think this programming style is *good* style in the
sense of making it easier to understand the program. Where applicable.
Anno
------------------------------
Date: Mon, 14 Aug 2006 21:44:24 +0100
From: Ben Morrow <benmorrow@tiscali.co.uk>
Subject: Re: PERL ---> Move email from Inbox folder to another or vice versa in OUTLOOK
Message-Id: <8u37r3-63v.ln1@osiris.mauzo.dyndns.org>
Quoth Brian Helterline <brian.helterline@hp.com>:
> -=-=-=-=-=-
MIME is not welcome on Usenet. Please don't do that again.
> bony_dev@yahoo.com wrote:
> > Hello Gurus,
> >
> > I am trying to write a perl script that will move an email message from
> > one folder to another folder in OUTLOOK using WIN32:OLE. Is there any
> > meathod to do so? If anybody has done it, please let me know...Thanks a
> > lot..
> >
> >
> > -Bony
> >
>
> This should point you in the right direction
>
> #!perl -w
-w is redundant with warnings.
> use strict;
> use warnings;
>
> use Win32::OLE;
> use Win32::OLE::Const 'Microsoft Outlook';
>
> # option variables
> my $verbose = 0; # set to 1 for debuggin
> my $all_items = 0; # set to 1 to process all mail, else only process unread
> my $filter = '[UnRead] = True';
>
> my $outlook;
>
> # use existing instance if Outlook is already running
>
> eval {$outlook = Win32::OLE->GetActiveObject('Outlook.Application')};
> die "Outlook not installed\n" if $@;
>
> unless (defined $outlook) {
> $outlook = Win32::OLE->new('Outlook.Application', 'Quit')
> or die "Oops, cannot start Outlook $^E\n";
> }
IMHO this would be clearer as
my $outlook = eval {
Win32::OLE->GetActiveObject('Outlook.Application')
or Win32::OLE->new('Outlook.Application', 'Quit')
or die "Cannot start Outlook: $^E";
};
$@ and die $@;
>
> my $ol = Win32::OLE::Const->Load($outlook);
You don't use this.
> my $item_idx = 1;
This needn't be declared this early.
> my $namespace = $outlook->GetNamespace("MAPI");
> my $inbox = $namespace->GetDefaultFolder(olFolderInbox);
>
>
> my $mail_count = $inbox->UnReadItemCount;
> $mail_count = $inbox->Items->Count if ( $all_items );
You end up calling $inbox->URIC even if you didn't need to.
my $mail_count = $all_items
? $inbox->UnReadItemCount
: $inbox->Items->Count;
You don't really need to do this at all if !$all_items.
> print STDERR "Item Count = $mail_count\n" if ($verbose);
>
> my $mail_items = $inbox->Items;
> my $item = $all_items ? $mail_items->Item(1) : $mail_items->Find($filter);
>
> while ($item) {
> if ($item->Class == olMail) { # skip non email (meeting requests, etc)
It would be cleaner to use loop control here, if you'd used a proper
continue block:
$item->Class == olMail or next;
> if ( $item->{'Subject'} eq 'subject') {
No need to quote 'Subject'.
> # do something with message
> }
> }
> if ( $all_items ) {
As this is the 'next' part of a C-style for loop, it should go in a
continue block
while ($item) {
...
}
continue {
if ($all_items) {
...
}
...
}
> if (++$item_idx > $mail_count) {
> $item = undef;
> }
This seems icky to me. Will the ->Items object really not return a
proper iterator, or an array?
> else {
> $item = $mail_items->Item($item_idx);
> }
> }
> else {
> $item = $mail_items->FindNext;
> }
> }
>
> undef $outlook;
Does this do anything?
> exit 0;
This is useless.
Ben
--
You poor take courage, you rich take care:
The Earth was made a common treasury for everyone to share
All things in common, all people one. [benmorrow@tiscali.co.uk]
'We come in peace'---the order came to cut them down.
------------------------------
Date: 14 Aug 2006 12:08:23 -0700
From: usenet@DavidFilmer.com
Subject: Re: Publicly flog David Filmer for writing multi-post flagging 'bot
Message-Id: <1155582503.276989.285390@i42g2000cwa.googlegroups.com>
Mumia W. wrote:
> VOTE:
> Publicly flog David Filmer for writing multi-post flagging 'bot:
I've been having a profitable discussion with John Bokma (another
critic of this idea) in another thread (http://tinyurl.com/rdedx) where
various aspects of this have been hashed out. Before binding me to the
pillar, prehaps folks might consider some of the issues we've both
raised.
I have been quite surprized by some of the negative reaction to my bot.
I will freely admit that it can be improved upon, but I hadn't expected
many people to object (or really care very much).
I had intended to open a thread to discuss the matter (prehaps with a
somewhat less prejudicial subject line). I'm always open to suggestions
and constructive criticism (which John has furnished, but which has
been somewhat lacking in other complaints).
--
David Filmer (http://DavidFilmer.com)
------------------------------
Date: 14 Aug 2006 13:13:36 -0700
From: usenet@DavidFilmer.com
Subject: Re: Publicly flog David Filmer for writing multi-post flagging 'bot
Message-Id: <1155586416.241374.74360@m79g2000cwm.googlegroups.com>
Michele Dondi wrote:
> BTW: I'll never really know when (if) it's disabled, since I already killfiled it.
Well, I'm probably gonna change the bot's handle to something kinder
and gentler, so you (and others) will need to killfile it again.
Sorry...
(the bot's handle is sort of a joke - a habitiual multiposter here once
accused me of being a "usenet cop" because I flagged his posts. I
thought that was an amusing label (there is, of course, no such thing
as a usenet cop - it's a community-moderated space, so we're all, in a
way, usenet cops, if we choose to encourage posting guidelines, which
many of us do. But I think that that humor is misplaced here)).
--
David Filmer (http://DavidFilmer.com)
------------------------------
Date: Mon, 14 Aug 2006 11:07:10 -0400
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: regex and utf8 characters (german umlauts)
Message-Id: <g69y7tr9x0h.fsf@CN1374059D0130.kendall.corp.akamai.com>
On 11 Aug 2006, benmorrow@tiscali.co.uk wrote:
> Quoth Ted Zlatanov <tzz@lifelogs.com>:
>> On 10 Aug 2006, benmorrow@tiscali.co.uk wrote:
>>> Quoth Ted Zlatanov <tzz@lifelogs.com>:
>>>> On 10 Aug 2006, ext-dirk.heinrichs@nokia.com wrote:
>>>>
>>>>> the following little perl snippet
>>>>>
>>>>> perl -e '($string = "AAA <c4><c4><c4> BBB CCC DDD") =~
>>>>> s/(\p{IsUpper}+)/\L\u\1\E/g; print $string . "\n"'
> <snip my comment>
>>>>> gives this result:
>>>>>
>>>>> Aaa <c4><c4><c4> Bbb Ccc Ddd
>>>>>
>>>>> How do I turn those umlauts into "<c4><e4><e4>" also? I tried adding
>>>>> "use utf8;", but that didn't help.
>>>>
>>>> The utf8 pragma won't make a difference. <e4> is ASCII code 196.
>>>
>>> There is No Such Thing as 'ASCII code 196'. ASCII only goes up to 127.
>>>
>>> As the post arrived here, the section of code represented above by
>>> '<c4><c4><c4>' is 3 bytes long. This is not valid UTF8, so if these
>>> three bytes are actually in your file you have a problem.
>>
>> The OP had a word made of three A-umlaut characters, to indicate that
>> the second and third were not lowercased automatically.
>
> The OP had three bytes 0xc4. Whether or not this is three A-umlaut
> characters depends on what encoding you are assuming the source is
> written in. In UTF-8, these three bytes are invalid. In ASCII, these
> three bytes are invalid. In ISO8859-1 they are three A-umlaut
> characters. In ISO8859-7 (to pick a random example) it is three capital
> deltas.
I checked the original article. It is encoded in utf-8. I don't know
where you got the <c4> from in your followup, but the text between
"AAA" and "BBB" correctly decodes to three A-umlauts in my newsreader
and to a UTF-8 capable terminal. I think your newsreader transformed
to 8859-1 encoding somehow. What I saw is three ocurrences of the
2-byte sequence 0xC384 that you can actually find at
http://home.tiscali.nl/t876506/utf8tbl.html as the first entry for
A-umlaut (Adieresis is the PostScript name for it, I guess). So
you're right in general terms, 0xC4 can mean many things, but here the
OP provided the correct text in the correct encoding.
> The ord of A-umlaut is 0xc4, yes. This is not relevant here: which bytes
> are used to represent a character depend on which encoding is in use.
>
> This is not just irrelevant nit-picking: it really matters. See
> http://www.joelonsoftware.com/articles/Unicode.html .
Thanks for the pointer. I'm pretty conversant with Unicode and
character encodings. I think you were looking at something strange in
your newsreader, hence the confusion. I compounded it by assuming you
actually saw three of the 0xC4 bytes in the original message. Sorry.
> [0] In case anyone gets the wrong idea, this is not a criticism. The
> problem required to be solved (work both with people who want proper
> Unicode handling and people who want to carry on assuming all charsets
> are single-byte supersets of ASCII, without anyone noticing anything
> weird's going on) is ultimately insoluble, and perl generally does a
> good job. When it doesn't it can always be persuaded to by the addition
> of appropriate calls to Encode.
Good advice. I advocate UTF-8 wherever possible, since it's compact,
unambigous, and can cover the whole UCS.
Ted
------------------------------
Date: Mon, 14 Aug 2006 19:38:40 +0100
From: Ben Morrow <benmorrow@tiscali.co.uk>
Subject: Re: regex and utf8 characters (german umlauts)
Message-Id: <gis6r3-0ht.ln1@osiris.mauzo.dyndns.org>
Quoth Ted Zlatanov <tzz@lifelogs.com>:
> On 11 Aug 2006, benmorrow@tiscali.co.uk wrote:
>
> > The OP had three bytes 0xc4. Whether or not this is three A-umlaut
> > characters depends on what encoding you are assuming the source is
> > written in. In UTF-8, these three bytes are invalid. In ASCII, these
> > three bytes are invalid. In ISO8859-1 they are three A-umlaut
> > characters. In ISO8859-7 (to pick a random example) it is three capital
> > deltas.
>
> I checked the original article. It is encoded in utf-8. I don't know
> where you got the <c4> from in your followup, but the text between
> "AAA" and "BBB" correctly decodes to three A-umlauts in my newsreader
> and to a UTF-8 capable terminal.
Yes, I went back and did the same, and, as they arrived here,
The original article appears to be in UTF8, with the string in
question represented by six bytes.
Your first reply (that I was replying to) recoded it as ISO8859-1,
with the string in question in three bytes.
This just re-emphasises what I said in my first reply: Usenet is an
ASCII medium. All posts are assumed to be in ASCII, and there is no way
to specify otherwise. So don't try to post in other character sets.
Ben
--
Every twenty-four hours about 34k children die from the effects of poverty.
Meanwhile, the latest estimate is that 2800 people died on 9/11, so it's like
that image, that ghastly, grey-billowing, double-barrelled fall, repeated
twelve times every day. Full of children. [Iain Banks] benmorrow@tiscali.co.uk
------------------------------
Date: Mon, 14 Aug 2006 15:16:15 -0400
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: regex and utf8 characters (german umlauts)
Message-Id: <g694pwf86ww.fsf@CN1374059D0130.kendall.corp.akamai.com>
On 14 Aug 2006, benmorrow@tiscali.co.uk wrote:
> Quoth Ted Zlatanov <tzz@lifelogs.com>:
>> On 11 Aug 2006, benmorrow@tiscali.co.uk wrote:
>>
>>> The OP had three bytes 0xc4. Whether or not this is three A-umlaut
>>> characters depends on what encoding you are assuming the source is
>>> written in. In UTF-8, these three bytes are invalid. In ASCII, these
>>> three bytes are invalid. In ISO8859-1 they are three A-umlaut
>>> characters. In ISO8859-7 (to pick a random example) it is three capital
>>> deltas.
>>
>> I checked the original article. It is encoded in utf-8. I don't know
>> where you got the <c4> from in your followup, but the text between
>> "AAA" and "BBB" correctly decodes to three A-umlauts in my newsreader
>> and to a UTF-8 capable terminal.
>
> Yes, I went back and did the same, and, as they arrived here,
>
> The original article appears to be in UTF8, with the string in
> question represented by six bytes.
>
> Your first reply (that I was replying to) recoded it as ISO8859-1,
> with the string in question in three bytes.
I think this was a decision made by Gnus automatically,
unfortunately. I thought it was preserving the original encoding. As
I said, sorry for the confusion.
Ted
------------------------------
Date: 14 Aug 2006 09:05:54 -0700
From: "Robert Hicks" <sigzero@gmail.com>
Subject: Re: UK Recruitment for Junior Perl Developer
Message-Id: <1155571554.323852.116050@h48g2000cwc.googlegroups.com>
Allan wrote:
> Robert Hicks wrote:
>
> > Allan wrote:
> > > Ladies and Gents. I am a Recruitment Consultant currently engaged by a
> > > client in North Yorkshire (Harrogate) to find 2 junior Perl Developers.
> > >
> > >
> > > The role will suit a recent graduate with 1 years commercial experience
> > > (either post grad or placement) who is looking for an entry level role.
> > > Our client needs Perl, PHP, MySQL and Apache experience. This is a
> > > permanent role with an expanding company where training and career
> > > progression are assured.
> > >
> > > If anybody is interested, please reply to this posting, e-mail me at
> > > allan dot wroe at mayfieldcurzon dot com or check out the job posting
> > > on
> > >
> > > http://www.jobserve.com/WA88D227B9222C3DC.job
> > >
> > > Happy hunting.
> >
> > Another place to post is: jobs.perl.org
> >
> > Robert
>
> Appreciated. Thanks Robert.
You are welcome...
Robert
------------------------------
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 9604
***************************************
