[28179] in Perl-Users-Digest
Perl-Users Digest, Issue: 9543 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Aug 1 06:05:45 2006
Date: Tue, 1 Aug 2006 03:05:05 -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, 1 Aug 2006 Volume: 10 Number: 9543
Today's topics:
AlphaX + Perl <petercolapietro@gmail.com>
Re: AlphaX + Perl usenet@DavidFilmer.com
Re: continous update (print) <jurgenex@hotmail.com>
Re: continous update (print) <dmercer@mn.rr.com>
foreach aliasing, my variables, and visibility in sub <register_allocation@lycos.com>
Re: foreach aliasing, my variables, and visibility in s <simon@unisolve.com.au>
Re: foreach aliasing, my variables, and visibility in s <bik.mido@tiscalinet.it>
Re: foreach aliasing, my variables, and visibility in s usenet@DavidFilmer.com
Re: perl editor <vfoley@gmail.com>
Re: perl editor <josef.moellers@fujitsu-siemens.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Printing Hash Marks During File Download <benmorrow@tiscali.co.uk>
Re: Printing Hash Marks During File Download usenet@DavidFilmer.com
Problem with DateTime <madan.narra@gmail.com>
Re: Problem with DateTime <sisyphus1@nomail.afraid.org>
Re: Sharing a socket between instances xhoster@gmail.com
Re: Strange characters using Term::Readline on Win32 <w.n.humann@agilent.com>
Re: Strange characters using Term::Readline on Win32 <w.n.humann@agilent.com>
Re: Using an input/csv file to rename files <josef.moellers@fujitsu-siemens.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 01 Aug 2006 00:11:07 GMT
From: Peter Colapietro <petercolapietro@gmail.com>
Subject: AlphaX + Perl
Message-Id: <C0F4145A.1CC%petercolapietro@gmail.com>
Hi I am running Mac OS X Version 10.4.7 on my MacBook Pro. I downloaded
Perl 5.8.8 and put it in /library/perl. I am using AlphaX as my texteditor
when I code for Perl. I also download Tcl/Tk Aqua Batteries as instructed.
I am going through O"reilly's Learning Perl. I created my first code:
#!/usr/bin/perl
print "Hello, world!\n";
I think I set everything up right in Config - Perl Mode Prefs. But when I
go to the Camal tab - tell perl - open this file
the Camal turns blue all around it and it just stays that way. When I hit
esc it says AESend failer: OSErr - 1711. If I try the camal tab - Run a
file and choose the Hello, world! file it says can't read "wname": no such
variable. I looked all through the wiki at
http://alphatcl.sourceforge.net/cgi-bin/wikit/24.html and the AlphaX website
but I can't seem to figure it out. Any help would be greatly appreciated.
------------------------------
Date: 1 Aug 2006 00:29:36 -0700
From: usenet@DavidFilmer.com
Subject: Re: AlphaX + Perl
Message-Id: <1154417376.268278.190160@b28g2000cwb.googlegroups.com>
Peter Colapietro wrote:
> [a multiposted question]
This question was multiposted to the Perl.Beginners newsgroup (Note to
JWK et al: I mean the usenet mirror of the perl.org mailing list, which
is available on every NNTP server that I know of, including,
unfortunately, those indexed by Google Groups).
See: http://tinyurl.com/kuk52
Please burn this thread (to discourage usenet rudeness)
--
David Filmer (http://DavidFilmer.com)
------------------------------
Date: Tue, 01 Aug 2006 03:22:25 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: continous update (print)
Message-Id: <RNzzg.3810$cj7.3562@trnddc01>
Lars Madsen wrote:
> if one e.g . wants to write a countdown one can do this as
>
> $|=1;
> ...
> # some loop
> printf "% 4d\r", $count;
>
> where \r then makes sure that we reprint on them same line over and
> over again.
> But what if you want to do this with several lines at once?
>
> I have a data structure with, say, 10 special entries that changes
> every second, I would like to have a continous overview if these
> numbers in the same fashion as above.
>
> How would one do that?
Use the Curses module to position the cursor before each output block.
jue
------------------------------
Date: Tue, 01 Aug 2006 03:44:04 GMT
From: "Dan Mercer" <dmercer@mn.rr.com>
Subject: Re: continous update (print)
Message-Id: <86Azg.16751$PN4.5153@tornado.rdc-kc.rr.com>
"Jürgen Exner" <jurgenex@hotmail.com> wrote in message news:RNzzg.3810$cj7.3562@trnddc01...
: Lars Madsen wrote:
: > if one e.g . wants to write a countdown one can do this as
: >
: > $|=1;
: > ...
: > # some loop
: > printf "% 4d\r", $count;
: >
: > where \r then makes sure that we reprint on them same line over and
: > over again.
: > But what if you want to do this with several lines at once?
: >
: > I have a data structure with, say, 10 special entries that changes
: > every second, I would like to have a continous overview if these
: > numbers in the same fashion as above.
: >
: > How would one do that?
:
: Use the Curses module to position the cursor before each output block.
:
: jue
:
:
That's probably overkill. Just use clear:
my $clear = `clear`;
chomp $clear;
print STDERR "${clear}whatever\nwhatever\n";
Dan Mercer
------------------------------
Date: Tue, 01 Aug 2006 06:12:41 GMT
From: "register_allocation" <register_allocation@lycos.com>
Subject: foreach aliasing, my variables, and visibility in sub
Message-Id: <thCzg.8262$157.5047@newsread3.news.pas.earthlink.net>
Consider the following script:
#!/usr/bin/perl -w
use strict;
my $v = '???';
foreach $v ('foo') {
print "in loop, \$v=$v\n";
process();
}
sub process { print "in process, \$v=$v\n" }
__END__
This prints
in loop, $v=foo
in process, $v=???
I get the same result on Win32/ActiveState v5.8.8 and Redhat v5.8.0.
Interestingly, if I change '$v' from a 'my' to an 'our' variable, it
prints
in loop, $v=foo
in process, $v=foo
Is this a known thing? Bug? Feature?
ra
------------------------------
Date: Tue, 01 Aug 2006 17:21:47 +1000
From: Simon Taylor <simon@unisolve.com.au>
Subject: Re: foreach aliasing, my variables, and visibility in sub
Message-Id: <eamvja$1hbt$1@otis.netspace.net.au>
Hello,
> This prints
> in loop, $v=foo
> in process, $v=???
>
> I get the same result on Win32/ActiveState v5.8.8 and Redhat v5.8.0.
> Interestingly, if I change '$v' from a 'my' to an 'our' variable, it
> prints
> in loop, $v=foo
> in process, $v=foo
>
> Is this a known thing? Bug? Feature?
Seet the commentary in perldoc perlsyn under " Foreach Loops"
The "foreach" loop iterates over a normal list value and
sets the variable VAR to be each element of the list in
turn. If the variable is preceded with the keyword "my",
then it is lexically scoped, and is therefore visible only
within the loop. Otherwise, the variable is implicitly
local to the loop and regains its former value upon exit
ing the loop.
For more on how foreach can localize the control variable see:
http://www.perlmeme.org/howtos/syntax/foreach.html
Hope this helps.
Regards,
Simon Taylor
--
www.perlmeme.org
------------------------------
Date: 1 Aug 2006 10:09:46 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: foreach aliasing, my variables, and visibility in sub
Message-Id: <bt2uc2pm1l5245dprnnq5u2uhfmung5bu9@4ax.com>
On Tue, 01 Aug 2006 06:12:41 GMT, "register_allocation"
<register_allocation@lycos.com> wrote:
>my $v = '???';
>foreach $v ('foo') {
> print "in loop, \$v=$v\n";
> process();
>}
>sub process { print "in process, \$v=$v\n" }
>
>__END__
>This prints
>in loop, $v=foo
>in process, $v=???
[snip]
>Is this a known thing? Bug? Feature?
^^^^^^^
^^^^^^^
process() is a closure around the variable $v lexically declared in
the sorrounding scope.
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: 1 Aug 2006 02:01:14 -0700
From: usenet@DavidFilmer.com
Subject: Re: foreach aliasing, my variables, and visibility in sub
Message-Id: <1154422874.458557.150560@h48g2000cwc.googlegroups.com>
register_allocation wrote:
> Is this a known thing? Bug? Feature?
Feature. You may appreciate a read-through of the O'Reilly book
"Advanced Perl Programming" (either edition, but I tend to favor the
Second Edition by Simon Cozens). The chapter on closures will answer
ALL your questions (and then some, and then some more).
--
David Filmer (http://DavidFilmer.com)
------------------------------
Date: 31 Jul 2006 16:08:11 -0700
From: "vfoley@gmail.com" <vfoley@gmail.com>
Subject: Re: perl editor
Message-Id: <1154387291.446519.327580@s13g2000cwa.googlegroups.com>
syracuse wrote:
> Hi
> anyone knows what is a good free editor to use for perl ?
> Thanks
> Syracuse
Emacs with cperl-mode work very well here.
------------------------------
Date: Tue, 01 Aug 2006 08:50:21 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: perl editor
Message-Id: <eamtml$7ob$2@nntp.fujitsu-siemens.com>
Abigail wrote:
> Josef Moellers (josef.moellers@fujitsu-siemens.com) wrote on MMMMDCCXVI=
I
> September MCMXCIII in <URL:news:eal0kq$f1r$1@nntp.fujitsu-siemens.com>:=
> @@ syracuse wrote:
> @@ > Hi
> @@ > anyone knows what is a good free editor to use for perl ?
> @@ > Thanks
> @@ > Syracuse=20
> @@ =20
> @@ vi?
>=20
>=20
> vi isn't free. Although many good vi clones are.
Hmm, didn't know that. I usually call "vim" as "vi".
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: 01 Aug 2006 07:22:28 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.6 $)
Message-Id: <44cf0134$0$57729$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, 1 Aug 2006 01:28:22 +0100
From: Ben Morrow <benmorrow@tiscali.co.uk>
Subject: Re: Printing Hash Marks During File Download
Message-Id: <6qj2q3-lkl.ln1@osiris.mauzo.dyndns.org>
Quoth HaroldWho <hlarons@yahoo.com>:
> I am using the Net::POP3 module to retrieve mail from a dialup POP3 server.
> The method 'get->(<msg number>)' returns a reference to an array which
> contains the lines of message text read from the server. So far, so good.
>
> Using dialup, large messages take some time to download, during which the
> program gives no indication that the d/l is going OK.
>
> I'd like to print hash marks during the d/l, much like an ftp d/l does, but
> I'm stumped for a way to do it, at using some kind of loop.
>
> Ideas?
Use ->getfh, read the data yourself and print whatever progress stuff
you like.
Ben
--
Giles: It's very common for Indian spirits to change to animal form.
Buffy: [...] and, 'Native American'. G: Sorry? B: We don't say 'Indian'.
G: Oh, right, yes; always behind on the terms... yes, still trying not to refer
to you lot as 'bloody colonials'. [Buffy, 'Pangs'] benmorrow@tiscali.co.uk
------------------------------
Date: 31 Jul 2006 18:21:16 -0700
From: usenet@DavidFilmer.com
Subject: Re: Printing Hash Marks During File Download
Message-Id: <1154395276.878453.63250@75g2000cwc.googlegroups.com>
HaroldWho wrote:
> I'd like to print hash marks during the d/l, much like an ftp d/l does, but
> I'm stumped for a way to do it, at using some kind of loop.
The trick is, the program must process the file a bit at a time
(instead of "slurping" it in one operation) so that it can periodically
update the user that something is happening.
I think you can do what you want if you adapt Ben's previous suggestion
(to use ->getfh) and slurp a bit at a time while updating a ticker.
Actually, you may prefer a spinner, and CPAN has a simple module,
Acme::Spinner, to help you out.
I've combined some code here from the CGI and Acme::Spinner perldocs to
give you an idea of what I'm talking about. I haven't tested this (and,
remember, the file I/O stuff is from CGI.pm), but you ought to be able
to do something rather like this.
use Acme::Spinner;
my $spinner = Acme::Spinner->new();
# Copy a binary file to somewhere safe
open (OUTFILE,">>/usr/local/web/users/feedback");
while ($bytesread=read($filename,$buffer,1024)) {
print STDERR $spinner->next(), "\r";
print OUTFILE $buffer;
}
I've used a technique like this to "dummy up" a progress indicator for
CGI file uploads. Modify the size of each chunk (ie, 1024) to vary the
speed of the spinner as appropriate for your typical connection speed.
--
David Filmer (http://DavidFilmer.com)
------------------------------
Date: 31 Jul 2006 23:20:28 -0700
From: "madan" <madan.narra@gmail.com>
Subject: Problem with DateTime
Message-Id: <1154413228.000556.70140@i3g2000cwc.googlegroups.com>
hi all,
i am installing the DateTime.pm on windows using nmake....
when i tried to install it i am getting an error saying
" Cant locate lodable object for module DateTime in @INC (@INC
contains: C:/perl/lib c:/perl/site/lib .) at
C:/perl/site/lib/DateTime.pm line 47"
can anyone please tell me how to use this module...
thanks in advance
madan
------------------------------
Date: Tue, 1 Aug 2006 19:51:19 +1000
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: Problem with DateTime
Message-Id: <44cf250a$0$22358$afc38c87@news.optusnet.com.au>
"madan" <madan.narra@gmail.com> wrote in message
news:1154413228.000556.70140@i3g2000cwc.googlegroups.com...
> hi all,
> i am installing the DateTime.pm on windows using nmake....
> when i tried to install it i am getting an error saying
> " Cant locate lodable object for module DateTime in @INC (@INC
> contains: C:/perl/lib c:/perl/site/lib .) at
> C:/perl/site/lib/DateTime.pm line 47"
>
I gather this is the error you get when you attempt to use the module.
It happens because, although DateTime.pm can be found, the compiled part of
the module (the dll - which is the "loadable object") cannot be found. This,
in turn, indicates that the build/install procedure did not work or was
performed incorrectly.
Assuming that the 'perl Makefile.PL' step proceeded without error, what was
the output of the 'nmake' , 'nmake test' and 'nmake install' steps.
Cheers,
Rob
------------------------------
Date: 31 Jul 2006 22:00:13 GMT
From: xhoster@gmail.com
Subject: Re: Sharing a socket between instances
Message-Id: <20060731180753.230$WL@newsreader.com>
"Derek Basch" <dbasch@yahoo.com> wrote:
> > > #member_id state could be changed here by another Member instance
> > > #calling the socket at the same time??????????
> > >
> > > # print to the GPS socket
> > > print $gps_socket $command, "\r\n";
> > >
> > > while (<$gps_socket>) {
> > > chop;
> > > last if /^###/;
> > > push (@response, $_);
> > > }
> > > throw Error::Simple("@response") if (grep(/Error/i, @response));
> >
> > In the absence of threads or fork (and the infinite recursion
> > previously mentioned), no _doCommand method serving a different Member
> > instance can seize control of the program during this code, so there
> > should be no problem with the state being changed.
>
> Thanks for the information. Is this idiom documented anywhere?
I don't think so, as I don't think there is anything to document!
> I
> couldn't seem to find anything on the subject of order of execution and
> locking for class variables. How does Perl know that the class variable
> filehandle (file_handle) which is being called by an instance (foo) is
> locked because a different instance (foo2) is already using that same
> filehandle (file_handle)?
It doesn't know that. In a single threaded program, there is only one
thread of execution. There is no need to lock the socket handle (or
a regular variable protecting the socket handle), because there is no one
to lock it against. You have the world all to yourself, you are the only
person driving on the roads. You don't have to install traffic lights,
because there is no one out there to hit. (You still need to be careful
not to run off the road and drive into a tree, or have a rock slide land on
your car, but that is a different matter.)
%SIG handlers should not read or write to the socket handle. But why would
they want to do that? _doCommand needs to not make recursive calls into
itself (either directly or indirectly) during the vulnerable part (between
the first print of the ID through the last read of the response to the
command). But why would it?
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: Tue, 01 Aug 2006 10:56:05 +0200
From: Wolfram Humann <w.n.humann@agilent.com>
Subject: Re: Strange characters using Term::Readline on Win32
Message-Id: <1154422130.760253@newsreg.cos.agilent.com>
Thomas Kratz wrote:
> Do you have a TERM environment variable? Try doing a
>
> set TERM=
>
> before running the script.
Yes, that's it. Some stupid program thought it should modify TERM *permanently*. Made sure it won't
do so anymore :-)
Thanks!
------------------------------
Date: Tue, 01 Aug 2006 11:00:02 +0200
From: Wolfram Humann <w.n.humann@agilent.com>
Subject: Re: Strange characters using Term::Readline on Win32
Message-Id: <1154422368.181907@newsreg.cos.agilent.com>
Sisyphus wrote:
> Yes, they look like ANSI escape sequences to me.
>
> I, too, cannot reproduce the behaviour (on Windows 2000) with any of the
> perls/shells that I have. Which shell are you running in - the cmd.exe
> shell, or the command.com shell, or some other shell ?
> Is there something you've installed/enabled that could be doing this ?
No difference between cmd.exe and command.com. (Actually, TERM was the problem -- see my other
reply). Thanks for your reply!
------------------------------
Date: Tue, 01 Aug 2006 08:49:28 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: Using an input/csv file to rename files
Message-Id: <eamtkv$7ob$1@nntp.fujitsu-siemens.com>
Terry wrote:
> My appologies for the 5 days inbetween posts, but I went on vacation
> and unplugged for a few days.
As in "I'll post this question now, then go on a vacation. Let them sort =
this out, discuss the pro's and con's and when I'm back, I can pick up a =
solution, without having participated in the discussion, shown what I=20
tried and where it failed, rectified false assumptions"?
26 to 31 ist exactly 5 days.
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
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 9543
***************************************
