[28756] in Perl-Users-Digest
Perl-Users Digest, Issue: 10120 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jan 5 09:06:04 2007
Date: Fri, 5 Jan 2007 06:05:05 -0800 (PST)
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, 5 Jan 2007 Volume: 10 Number: 10120
Today's topics:
Re: Elegant equivalent to this regex? <jurgenex@hotmail.com>
Re: File::Temp and external editor <joe@inwap.com>
Re: gtk2 treeview and threads : custom sort while updat erwan.barrier@gmail.com
How can I use the password and username stored in cooki wqhflp@gmail.com
Indirect function call via Name <ronaldf@eml.cc>
Re: Indirect function call via Name anno4000@radom.zrz.tu-berlin.de
Re: Iterate through words in a string <someone@example.com>
Re: Perl examples in many other languages <paddy3118@netscape.net>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Problematic Perl code <joe@inwap.com>
Re: Problematic Perl code <joe@inwap.com>
Re: which email module - MIME::LITE, Email::Send, other <tintin@invalid.invalid>
Writing UTF-8 file under Windows t_lawetta@yahoo.com
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 05 Jan 2007 08:32:29 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Elegant equivalent to this regex?
Message-Id: <x2onh.4507$Uf.1313@trndny07>
sherifffruitfly wrote:
> usenet@DavidFilmer.com wrote:
>> sherifffruitfly wrote:
>>> (2) Capture all of the digits, leaving the quotes and commas for the
>>> garbage man.
>>
>> If you just want to strip out the non-numerics why futz with regexps?
>> Why not just use s/// to get rid of the non-numerics?
>>
>> my $original = " 123, 456, 789 ' ";
>> (my $numbers = $original) =~ s/\D//g ;
>> print $numbers;
>
> Because I want to use regex, please.
???
/\D/ _is_ a regular expression. If you mean something else by 'regex' then
please explain.
jue
------------------------------
Date: Fri, 05 Jan 2007 03:25:43 -0800
From: Joe Smith <joe@inwap.com>
Subject: Re: File::Temp and external editor
Message-Id: <2NKdnUhurrVZqAPYnZ2dnUVZ_rzinZ2d@comcast.com>
Brian McCauley wrote:
>> What I am doing at the moment is @cmdbuf = `cat $filename`; so that I
>> can continue with the rest of my code, but I'd like to know how to do it
>> better.
>
> I think you are looking for
>
> seek($fh,0,0);
> @cmdbuf = <$fh>;
If you're using an editor that creates a backup file, that may not work.
Better to re-open the file after the editor is done with it.
-Joe
------------------------------
Date: 5 Jan 2007 04:22:05 -0800
From: erwan.barrier@gmail.com
Subject: Re: gtk2 treeview and threads : custom sort while updating rows
Message-Id: <1167999725.277835.284380@v33g2000cwv.googlegroups.com>
hello
thanks for answering.
So here is an example without threads that works well :
use strict;
use Gtk2 qw/-init/;
use Gtk2::SimpleList;
use vars qw($count);
$count = 0;
my $win = Gtk2::Window->new;
my $tree = Gtk2::SimpleList->new('test' => 'int',);
$tree->get_column(0)->set_sort_column_id(0);
$tree->get_model->set_sort_func(0, \&sort_int);
$win->add($tree);
$win->show_all;
Glib::Timeout->add(500, \&update_action, $tree);
Gtk2->main;
sub update_action
{
my $tree = shift;
push @{$tree->{data}}, $count++;
}
sub sort_int
{
my ($list, @iter) = @_;
@iter = map {$_ = $list->get($_, 0);$_} @iter;
return ($iter[0] <=> $iter[1]);
}
Now the same example with threads :
use strict;
use Gtk2 qw/-init -threads-init/;
use Gtk2::SimpleList;
use Glib qw (TRUE FALSE);
use threads;
use threads::shared;
use vars qw($count);
die "Glib::Object thread safetly failed"
unless Glib::Object->set_threadsafe (TRUE);
share($count);
$count = 0;
my $win = Gtk2::Window->new;
my $tree = Gtk2::SimpleList->new('test' => 'int',);
$tree->get_column(0)->set_sort_column_id(0);
# set_sort_func set the custom sorting func
#if removed the automatically sorting func works
$tree->get_model->set_sort_func(0, \&sort_int);
$win->add($tree);
$win->show_all;
Glib::Timeout->add(500, sub {threads->create(\&update_action, $tree)});
Gtk2->main;
sub update_action
{
my $tree = shift;
Gtk2::Gdk::Threads->enter;
push @{$tree->{data}}, $count++;
Gtk2::Gdk::Threads->leave;
}
sub sort_int
{
my ($list, @iter) = @_;
@iter = map {$_ = $list->get($_, 0);$_} @iter;
return ($iter[0] <=> $iter[1]);
}
the error message is :
"Usage: Gtk2::TreeModel::iter_n_children(tree_model, iter=NULL)"
> Please post a complete working snippet which demonstrates
> the problem. Perl/Gtk2 tries to be thread-safe, but it is tricky
> to use, and we cannot test it without working code.
>
> It may be as simple as
>
> use Gtk2 qw/-init -threads-init /;
> die "Glib::Object thread safetly failed"
> unless Glib::Object->set_threadsafe (TRUE);
>
> The enter-leave mechanism is tricky to use, and it is usually
> best to use the standard thread-gui precautions....
>
> 1. create your threads before any gui code
> 2. don't try to access the gui from the threads
>
> Now Perl/Gtk2's thread-safe mechanism tries to let you
> avoid those precautions, but it must be done right.
> So show complete snippets.
>
> zentara
>
------------------------------
Date: 5 Jan 2007 00:49:11 -0800
From: wqhflp@gmail.com
Subject: How can I use the password and username stored in cookie files to access the web automatically
Message-Id: <1167986951.134397.184210@11g2000cwr.googlegroups.com>
To access some websites, not only the username/pwd is need, but also a
field need to fill based on a randomly generated digitals/letters on an
image(this will prevent the automatically account creating, such as
when creating the MSN account, the website will ask us to fill that
kind of data).
When I first accessed the website using firefox or IE, I must fill the
username/pwd and that kind of field. And if I close the browser and
open it a second time to view the same website, there is no need for me
to fill username/pwd which means firefox/IE can use the cookie to
access it. And I tried to use the cookie using be IE by model
HTTP::Cookies::Microsoft in the code, but the response from the web
server still can NOT recogize that I already logged in.
my $cookie_jar = HTTP::Cookies::Microsoft->new(
file => "$cookies_dir\\index.dat",
'delayload' => 0,
);
my $mech=WWW::Mechanize->new(cookie_jar=>$cookie_jar);
$mech->get("http://bbs1.21our.com/");
$mech->cookie_jar($cookie_jar);
die "Can't evan get the home pages" unless $mech->success;
my $output_page=$mech->content();
------------------------------
Date: Fri, 05 Jan 2007 11:28:32 +0100
From: Ronald Fischer <ronaldf@eml.cc>
Subject: Indirect function call via Name
Message-Id: <1167992912.79@user.newsoffice.de>
What would be the best (most elegant) way to solve the following:
Suppose I have the name of a function (i.e. not a coderef) as a
string, and I would like to call this function, passing to it
all the parameters of the current function (i.e. @_). For example:
our $func="bar";
sub foo
{
# Of course the following would not work
&$func(@_);
}
foo('x',5); # This is supposed to call &bar('x',5)
The above would work if $func were a code ref, but it is a string.
I came to the following solution which works, but is ugly:
use Data::Dumper;
sub foo
{
local $Data::Dumper::Terse=1; # No varnames
local $Data::Dumper::Indent=0; # No newlines
eval("$func(".join(',',Dumper(@_)).')');
}
Could someone suggest a better alternative?
Ronald
--
Ronald Fischer <ronaldf@eml.cc>
Posted via http://www.newsoffice.de/
------------------------------
Date: 5 Jan 2007 11:19:04 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Indirect function call via Name
Message-Id: <506qh8F1cj1n2U1@mid.dfncis.de>
Ronald Fischer <ronaldf@eml.cc> wrote in comp.lang.perl.misc:
> What would be the best (most elegant) way to solve the following:
>
> Suppose I have the name of a function (i.e. not a coderef) as a
> string, and I would like to call this function, passing to it
> all the parameters of the current function (i.e. @_). For example:
>
> our $func="bar";
>
> sub foo
> {
> # Of course the following would not work
> &$func(@_);
> }
What makes you think it doesn't work? Switch off strict 'refs' and
it does.
Anno
------------------------------
Date: Fri, 05 Jan 2007 09:39:17 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Iterate through words in a string
Message-Id: <91pnh.113207$YV4.24051@edtnps89>
Mirco Wahab wrote:
> Thus spoke Gonzalo Castro (on 2007-01-04 19:57):
>
>>I'm have a string I am constructing with space delimited words. I would like
>>to iterate through each word later. I thought making an array from the
>>contents of the string would be the convenient way to approach this but I'm
>>not having any luck. Any ideas?
>
> Better done like this (using your style and making a working example):
>
> use strict;
> use warnings;
>
> sub getMeAnotherString { time }
>
> my $accumulator;
> my $done = 5;
>
> while (not !$done--) {
Just as with the English language, you shouldn't use a double negative. :-)
while ($done--) {
John
--
Perl isn't a toolbox, but a small machine shop where you can special-order
certain sorts of tools at low cost and in short order. -- Larry Wall
------------------------------
Date: 5 Jan 2007 04:45:15 -0800
From: "Paddy3118" <paddy3118@netscape.net>
Subject: Re: Perl examples in many other languages
Message-Id: <1168001115.143581.177060@s34g2000cwa.googlegroups.com>
Paddy3118 wrote:
> Hi,
> I seem to have lost my reference to a web site with a series of around
> 100 simple Perl examples that have been implemented in other languages.
> I think the Perl examples might have originally come from a book.
> I do remember that there was a page that gave the percentage of the
> original Perl examples that had been covered by other languages.
> The other languages included both Ruby and Python as well as others.
>
> I have googled, but without success.
>
> Thanks, Paddy.
I've finally found it:
http://pleac.sourceforge.net/
- Paddy.
------------------------------
Date: 05 Jan 2007 08:10:15 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <459e07e6$0$81351$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.7 $)
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 that they do
know and are being the "bad kind" of Lazy.
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, 05 Jan 2007 02:25:50 -0800
From: Joe Smith <joe@inwap.com>
Subject: Re: Problematic Perl code
Message-Id: <BpadnYxchrYhugPYnZ2dnUVZ_veinZ2d@comcast.com>
Eric Schwartz wrote:
> "PerlNovice" <mfarid1@yahoo.com> writes:
>> 1)I need to copy .zip files from Windows to my Unix folder and name the
>> .zip files as something else, let's say, .txt. I then need
>> to rename it back to .zip only when the entire file has been copied.
>
> Why?
So that the partially copied file won't be accessible.
So that any existing file will can be accessed while the transfer is
in progress.
1) Copy the file to the destination directory using a temporary name.
2) When the transfer is complete (which could take hours), delete the
existing file (if any) and rename the temporary file to its proper name.
It's the right thing to do on a multi-user or multitasking system.
> It's not considered polite in this newsgroup to ask people to read
> documentation for you if you can read it yourself.
You've completely missed the point of what PerlNovice was asking.
Reading the documentation on get() is not the answer in this case.
-Joe
------------------------------
Date: Fri, 05 Jan 2007 03:15:12 -0800
From: Joe Smith <joe@inwap.com>
Subject: Re: Problematic Perl code
Message-Id: <m--dnUvvX-HQrgPYnZ2dnUVZ_qunnZ2d@comcast.com>
PerlNovice wrote:
> ... copy .zip files from Windows to my Unix folder and name the
> .zip files as something else, let's say, .txt. I then need
> to rename it back to .zip only when the entire file has been copied.
Using ".txt" is a bad idea. It is better to use ".part" or ".partial"
to indicate that the file being received is not yet complete.
> $ftp->cwd("/myfolder")
> or die "Cannot change working directory ", $ftp->message;
Do you really want use a name with a leading slash? Typical values for cwd()
are "myfolder" or "directory/subdirectory" for folders relative to your
login directory, or an absolute pathname like "/home/myname/mydir";
> for( <*.zip> ){
You've got a conceptual error there. That glob operator returns a list
of files that already exist on your local machine. To get a list of
available files on the FTP server, you need to ask the server and then
parse the results.
my @directory_listing = $ftp->dir() or die "Error ftp->dir() - ",$ftp->message;
print "Files on server:\n", join "\n",@directory_listing,'' if $verbose;
for my $line (@directory_listing) {
# WARNING: Not all FTP servers use the Unix format for dir().
my($perms,$links,$uid,$gid,$size,$mon,$day,$time,$file) = split ' ',$line,9;
next unless $file =~ /\.zip$/i;
> $ftp->get($_,"tmp.$$") or die $!;
> $ftp->rename("tmp.$$",$_) or die $!;
That's wrong. You need rename(), not $ftp->rename().
my $temp_name = "$file.$$.partial";
if ($ftp->get($file,$temp_name)) {
-f $file and (unlink $file or warn "Could not remove old $file: $!\n");
rename($temp_name,$name) or warn "Could not set name to $file: !$\n";
} else {
warn "get($file) failed: ", $ftp->message;
}
> $ftp->size($_) == -s $_ or die "$_ sizes don't match";
my $received = -s $file;
$received == $size or warn "Size mismatch for $file: $received != $size\n";
> }
>
> I would appreciate any help from anyone.
You can look at http://www.inwap.com/tivo/from-tivo as an example.
-Joe
------------------------------
Date: Fri, 5 Jan 2007 22:45:07 +1300
From: "Tintin" <tintin@invalid.invalid>
Subject: Re: which email module - MIME::LITE, Email::Send, other?
Message-Id: <459e105b$0$4779$88260bb3@free.teranews.com>
<brewsterbear@googlemail.com> wrote in message
news:1167951139.523928.118730@v33g2000cwv.googlegroups.com...
> Hi,
>
> Just wondering which is the "preferred" way to send email, possibly
> with attachments. I noticed MIME::Lite hasn't been developed for a few
> years, not that it really needs development. Are people using
> Email::Send or Mail::Send? Any recommendation appreciated.
I've found MIME::Lite to be very robust, flexible and simple to install and
use. And while MIME::Lite hasn't been updated for a while (it works just
fine), there are a number of related modules that are updated recently, eg:
MIME::Lite::HTML was updated Sep 2006.
--
Posted via a free Usenet account from http://www.teranews.com
------------------------------
Date: 5 Jan 2007 05:37:16 -0800
From: t_lawetta@yahoo.com
Subject: Writing UTF-8 file under Windows
Message-Id: <1168004236.108377.171710@11g2000cwr.googlegroups.com>
Happy New Year,
Whatever I try to write a UTF-8 file, I always end up with UTF-16LE
with the "FF FE" BOM at the beginning and 2 bytes per character.
I am reading strings from an external resource and try to write to
files.
my $string_with_special_chars =3D "Ch=E2teau M=FCller\nGar=E7on";
open F, ">:utf8", "test.txt";
print F $string_with_special_chars;
close F;
Tried it both on Linux (Perl 5.8.6) and Windows (Perl 5.8.7).
(In case you cannot see it: The string contains the chars with
the corresponding HTML entities acirc, uuml and ccedil.
Opening test.txt with my editor (Ultra-Edit) shows me the correct
string, but in hex view I see the "FF FE" BOM and it shows
2 bytes per character, e.g. 0x43 0x00 for the 'C' and
0xE7 0x00 for the ccedil.
Normally I am reading data via LDAP, so 'use utf8' is not required.
If I add it here, I get:
Malformed UTF-8 character (unexpected non-continuation byte 0x74,
immediately after start byte 0xe2) at ./test.pl line 4.
I tried to make sure my input strings are correctly decoded etc., but
no way.
As long as my strings stay within 7-bit ASCII it is fine, but after
that Perl always things it has to write a BOM and decode in a 2-byte
format.
Using Encode to write utf-8 results in a double encoding or at least
some unreadable chars.
Where does the BOM come from?
Why does Perl add it?
Doesn't Perl write UTF-8 by default?
Thank you for any hints. The issue cost me days already and yes, I have
read a lot about Perl and Unicode.
Tony
------------------------------
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 10120
****************************************
