[24261] in Perl-Users-Digest
Perl-Users Digest, Issue: 6452 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 23 11:10:45 2004
Date: Fri, 23 Apr 2004 08:10:17 -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 Fri, 23 Apr 2004 Volume: 10 Number: 6452
Today's topics:
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Problems with perlapi and PL_sv_undef (Mladen Georgiev)
RFC: Text similarity <tore@aursand.no>
Running Perl From Web Page W/out Changing Page? <hal@thresholddigital.com>
Re: Running Perl From Web Page W/out Changing Page? <noreply@gunnar.cc>
substitution from command line <Geezer@Freezer.com>
Re: substitution from command line BreadWithSpam@fractious.net
Re: substitution from command line <mothra@mothra.pub>
time configuration for localtime <wi@rjsolutions.org>
Re: time configuration for localtime <trammell+usenet@hypersloth.invalid>
Re: time configuration for localtime <noreply@gunnar.cc>
Re: time configuration for localtime <wi@rjsolutions.org>
Re: time configuration for localtime <wi@rjsolutions.org>
Re: time configuration for localtime <noreply@gunnar.cc>
Re: time configuration for localtime <tore@aursand.no>
Re: time configuration for localtime <wi@rjsolutions.org>
Re: time configuration for localtime <xx087@freenet.carleton.ca>
What kind of RegEx should I use for <TEXTAREA>? <NewsGroups@US-Webmasters.com>
Re: What kind of RegEx should I use for <TEXTAREA>? <spamtrap@dot-app.org>
Win32::OLE SaveAs Need to force Yes (Pat)
Re: Win32::OLE SaveAs Need to force Yes <1usa@llenroc.ude>
Re: Win32::OLE SaveAs Need to force Yes <1usa@llenroc.ude>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 23 Apr 2004 02:22:08 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <NrudncYnUrC9WRXdRVn-hQ@august.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: 23 Apr 2004 00:32:52 -0700
From: dziftar@yahoo.com (Mladen Georgiev)
Subject: Problems with perlapi and PL_sv_undef
Message-Id: <eaeceea5.0404222332.5ebbaed7@posting.google.com>
Hello!
I'm trying to call a perl subroutine from a C++ program via perlapi.
Here is the perl code
sub SaveDocuments {
my ( $files, @questions ) = @_;
...
}
In that subroutine $files must be array reference.
If I push &PL_sv_undef value for $files (there are no files)
XPUSHs( &PL_sv_undef );
$files is assigned the first element of @questions array (the rest of
parameters array).
Hereis how I fill @questions array in C++ code:
if ( Document->Questions != NULL ) {
for ( int i=0; i < Document->Questions->Count; i++ )
{
XPUSHs(sv_2mortal(newSVpv(Document->Questions[i],strlen(
Document->Questions[i] ) )));
}
}
Where am I wrong?
Thanks in advance!
Best regards,
Mladen
------------------------------
Date: Fri, 23 Apr 2004 14:16:53 +0200
From: Tore Aursand <tore@aursand.no>
Subject: RFC: Text similarity
Message-Id: <pan.2004.04.23.12.16.22.258554@aursand.no>
Hi!
I have a large (more than 3,000 at the moment) set of documents in various
formats (mostly PDF and Word). I need to create a sort of (...) index of
these documents based on their similarity. I thought it would be nice to
gather some suggestions from the people in this group before I proceeded.
First of all: Converting the documents to a more sensible format (text in
my case) is not the problem. The problem is the indexing and how to store
the data which represents the similarity between the documents.
I've done a search on CPAN and found a few modules which is of interest,
primarily AI::Categorize and WordNet. I haven't used any of these before,
but it seems like WordNet is the most appropriate one; AI::Categorize
seems to require you to categorize some of the documents first (which I
don't have the opportunity to do).
Are there any other modules I should take a look at? Any suggestions on
how I should deal with this task? Something you think I might forget?
Some traps I should look out for?
Any comments are appreciated! Thanks.
--
Tore Aursand <tore@aursand.no>
"First get your facts; then you can distort them at your leisure."
(Mark Twain)
------------------------------
Date: Fri, 23 Apr 2004 14:29:10 GMT
From: Hal Vaughan <hal@thresholddigital.com>
Subject: Running Perl From Web Page W/out Changing Page?
Message-Id: <VK9ic.11097$IW1.736155@attbi_s52>
Is there any way to run a Perl script from a web page without changing the
web page?
I'd like to be able to click a button on a web page and have it run a script
in the background, but not have to re-load the page or change anything. Is
this possible?
Thanks!
Hal
------------------------------
Date: Fri, 23 Apr 2004 16:47:48 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Running Perl From Web Page W/out Changing Page?
Message-Id: <c6bao5$9v573$1@ID-184292.news.uni-berlin.de>
Hal Vaughan wrote:
> Is there any way to run a Perl script from a web page without
> changing the web page?
>
> I'd like to be able to click a button on a web page and have it run
> a script in the background, but not have to re-load the page or
> change anything. Is this possible?
Yes. Provided that the only thing the script prints to STDOUT is:
print "Status: 204 No Content\n\n";
you should be able to invoke it the way you describe.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 23 Apr 2004 14:07:21 +0100
From: Geezer From The Freezer <Geezer@Freezer.com>
Subject: substitution from command line
Message-Id: <40891509.AD67497F@Freezer.com>
trying to change a string in a file
perl -e s/dogshit/catshit/g filename
Seems to do nothing - what am I doing wrong?
------------------------------
Date: 23 Apr 2004 09:30:06 -0400
From: BreadWithSpam@fractious.net
Subject: Re: substitution from command line
Message-Id: <yobad12sty9.fsf@panix2.panix.com>
Geezer From The Freezer <Geezer@Freezer.com> writes:
> perl -e s/dogshit/catshit/g filename
> Seems to do nothing - what am I doing wrong?
It's equivalent to writing a script like this:
#!/usr/bin/perl
s/dogshit/catshit/g;
and then running that script like this:
perl myscript filename
You've never actually opened filename up for reading,
nor have you looped through the contents of it, nor
printed out anything (ie. back to the file or to a
new file).
Take a look at the -n and -p (and the -i) command
line options for perl
man perlrun
--
Plain Bread alone for e-mail, thanks. The rest gets trashed.
No HTML in E-Mail! -- http://www.expita.com/nomime.html
Are you posting responses that are easy for others to follow?
http://www.greenend.org.uk/rjk/2000/06/14/quoting
------------------------------
Date: Fri, 23 Apr 2004 14:39:13 +0100
From: "Mothra" <mothra@mothra.pub>
Subject: Re: substitution from command line
Message-Id: <c6b687$rul$1@news8.svr.pol.co.uk>
"Geezer From The Freezer" <Geezer@Freezer.com> wrote in message
news:40891509.AD67497F@Freezer.com...
> trying to change a string in a file
>
> perl -e s/dogshit/catshit/g filename
>
> Seems to do nothing - what am I doing wrong?
You should be running:
perl -pi -we 's/dogshit/catshit/g' filename
------------------------------
Date: Fri, 23 Apr 2004 08:27:54 -0400
From: "Rich Bogle" <wi@rjsolutions.org>
Subject: time configuration for localtime
Message-Id: <c6b24a$2itu$1@msunews.cl.msu.edu>
I need to format the output from localtime below to have a 2 digit year, 2
digit month, and 2 digit day. If my memory serves right I believe there are
formatting options for localtime but cannot find reference to them. If they
don't exist I could format this the long way. I need the above format to
compare to folders that are named by the above date format.
sub currentdate {
#Get Current Date / Time
($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime;
$year = $year + 1900;
$mon = $mon + 1;
$curdate = $year . $mon . $mday;
print $curdate . "\n";
}
Thanks,
Rich
------------------------------
Date: Fri, 23 Apr 2004 12:55:16 +0000 (UTC)
From: "John J. Trammell" <trammell+usenet@hypersloth.invalid>
Subject: Re: time configuration for localtime
Message-Id: <slrnc8i4hk.ujr.trammell+usenet@hypersloth.el-swifto.com.invalid>
On Fri, 23 Apr 2004 08:27:54 -0400, Rich Bogle <wi@rjsolutions.org> wrote:
> I need to format the output from localtime below to have a 2 digit
> year, 2 digit month, and 2 digit day.
How about something along the lines of:
use POSIX 'strftime';
my $curdate = strftime("%y%m%d",localtime);
------------------------------
Date: Fri, 23 Apr 2004 14:55:16 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: time configuration for localtime
Message-Id: <c6b44t$9v45l$1@ID-184292.news.uni-berlin.de>
Rich Bogle wrote:
> I need to format the output from localtime below to have a 2 digit
> year, 2 digit month, and 2 digit day. If my memory serves right I
> believe there are formatting options for localtime but cannot find
> reference to them.
There are quite a few modules available that may help you format
dates; John mentioned one of them. Check out CPAN.
> If they don't exist I could format this the long way. I need the
> above format to compare to folders that are named by the above date
> format.
>
> sub currentdate {
> #Get Current Date / Time
> ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime;
> $year = $year + 1900;
> $mon = $mon + 1;
> $curdate = $year . $mon . $mday;
> print $curdate . "\n";
> }
That does not match your description since it prints a 4 digit year
and does not format the month and day to 2 digits.
Nevertheless, IMO "the long way" isn't very long in this case. And it
can be written even shorter:
sub currentdate {
my ($day,$mon,$year) = (localtime)[3..5];
printf "%02d%02d%02d\n", $year % 100, $mon + 1, $day;
}
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 23 Apr 2004 09:22:08 -0400
From: "Rich Bogle" <wi@rjsolutions.org>
Subject: Re: time configuration for localtime
Message-Id: <c6b5a2$2lte$1@msunews.cl.msu.edu>
"John J. Trammell" <trammell+usenet@hypersloth.invalid> wrote in message
news:slrnc8i4hk.ujr.trammell+usenet@hypersloth.el-swifto.com.invalid...
> On Fri, 23 Apr 2004 08:27:54 -0400, Rich Bogle <wi@rjsolutions.org> wrote:
> > I need to format the output from localtime below to have a 2 digit
> > year, 2 digit month, and 2 digit day.
>
> How about something along the lines of:
>
> use POSIX 'strftime';
> my $curdate = strftime("%y%m%d",localtime);
>
This option is perfect. strftime must be what I was thinking of. I will
just add a %H%M into the format and I will be good to go.
THANKS!
------------------------------
Date: Fri, 23 Apr 2004 09:42:43 -0400
From: "Rich Bogle" <wi@rjsolutions.org>
Subject: Re: time configuration for localtime
Message-Id: <c6b6gl$2n4k$1@msunews.cl.msu.edu>
"John J. Trammell" <trammell+usenet@hypersloth.invalid> wrote in message
news:slrnc8i4hk.ujr.trammell+usenet@hypersloth.el-swifto.com.invalid...
> On Fri, 23 Apr 2004 08:27:54 -0400, Rich Bogle <wi@rjsolutions.org> wrote:
> > I need to format the output from localtime below to have a 2 digit
> > year, 2 digit month, and 2 digit day.
>
> How about something along the lines of:
>
> use POSIX 'strftime';
> my $curdate = strftime("%y%m%d",localtime);
>
I now have:
sub daterange {
#Get Date / Time 1 year ago
use POSIX;
$format = "%y%m%d%H%M";
$curdate = strftime($format, localtime);
print $curdate . "\n";
#Date one year ago
$curdate = $curdate - 100000000;
print $curdate . "\n";
}
I need the date for one year ago, however if I do math on a year alone or as
above the leading 0 is eliminated. I need to preserver this leading 0. Do
you know of any options to do so. printf was mentioned in another post, but
is not suitable as I need to hold the info in a variable for some other
operations.
Thanks,
Rich
------------------------------
Date: Fri, 23 Apr 2004 15:49:44 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: time configuration for localtime
Message-Id: <c6b7b5$9k40t$1@ID-184292.news.uni-berlin.de>
Rich Bogle wrote:
> printf was mentioned in another post, but is not suitable as I need
> to hold the info in a variable for some other operations.
Then you can use sprintf() instead.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 23 Apr 2004 16:10:50 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: time configuration for localtime
Message-Id: <pan.2004.04.23.14.03.20.893080@aursand.no>
On Fri, 23 Apr 2004 08:27:54 -0400, Rich Bogle wrote:
> I need to format the output from localtime below to have a 2 digit year,
> 2 digit month, and 2 digit day. If my memory serves right I believe
> there are formatting options for localtime but cannot find reference to
> them.
No? Why didn't you read 'perldoc -f localtime', then? If _my_ memory
serves me right, there is an example there using 'sprintf' to format the
year to only show two digits.
> sub currentdate {
> #Get Current Date / Time
> ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime;
> $year = $year + 1900;
> $mon = $mon + 1;
> $curdate = $year . $mon . $mday;
> print $curdate . "\n";
> }
Untested:
sub currentdate {
my ($day, $month, $year) = (localtime)[3..5];
printf('%02d%02d%02d', $year % 100, $month + 1, $day);
}
--
Tore Aursand <tore@aursand.no>
"Leadership is doing what is right when no one is watching." (George
Van Valkenburg)
------------------------------
Date: Fri, 23 Apr 2004 10:38:36 -0400
From: "Rich Bogle" <wi@rjsolutions.org>
Subject: Re: time configuration for localtime
Message-Id: <c6b9pe$2q1d$1@msunews.cl.msu.edu>
"Gunnar Hjalmarsson" <noreply@gunnar.cc> wrote in message
news:c6b7b5$9k40t$1@ID-184292.news.uni-berlin.de...
> Rich Bogle wrote:
> > printf was mentioned in another post, but is not suitable as I need
> > to hold the info in a variable for some other operations.
>
> Then you can use sprintf() instead.
>
> --
> Gunnar Hjalmarsson
> Email: http://www.gunnar.cc/cgi-bin/contact.pl
>
I so need more caffeine this morning.
------------------------------
Date: 23 Apr 2004 14:41:00 GMT
From: Glenn Jackman <xx087@freenet.carleton.ca>
Subject: Re: time configuration for localtime
Message-Id: <slrnc8iao0.nel.xx087@smeagol.ncf.ca>
Rich Bogle <wi@rjsolutions.org> wrote:
> I need the date for one year ago, however if I do math on a year alone or as
> above the leading 0 is eliminated. I need to preserver this leading 0. Do
> you know of any options to do so. printf was mentioned in another post, but
> is not suitable as I need to hold the info in a variable for some other
> operations.
Manipulate the year in the list returned by localtime.
use POSIX 'strftime';
my @time = localtime;
my $fmt = '%y%m%d%H%M';
my $today = strftime($fmt, @time), "\n";
$time[5]--;
my $lastyear = strftime($fmt, @time), "\n";
--
Glenn Jackman
NCF Sysadmin
glennj@ncf.ca
------------------------------
Date: Fri, 23 Apr 2004 02:21:15 -0500
From: "W. D." <NewsGroups@US-Webmasters.com>
Subject: What kind of RegEx should I use for <TEXTAREA>?
Message-Id: <4088C3EB.2A40@US-Webmasters.com>
Hi Folks,
If a form has a <TEXTAREA> box to input all sorts of free-form
text, is it necessary to do a regular expressions validation?
That is, are there any dangerous characters that shouldn't be
allowed?
If so, what would that be?
Profuse 'thank-yous' in advance for any light you can shed!
--
Start Here to Find It Fast!™ ->
http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names -> http://domains.us-webmasters.com/
------------------------------
Date: Fri, 23 Apr 2004 03:44:43 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: What kind of RegEx should I use for <TEXTAREA>?
Message-Id: <TZidnYWdyIL1VBXdRVn-iQ@adelphia.com>
W. D. wrote:
> If a form has a <TEXTAREA> box to input all sorts of free-form
> text, is it necessary to do a regular expressions validation?
> That is, are there any dangerous characters that shouldn't be
> allowed?
You haven't really given enough context for anyone to provide a useful
answer; quite a bit depends on what you're going to do with the text.
For example, if you're going to store it in a database that only understands
ASCII text, then you'll need to scan the text for characters outside of the
ASCII range and encode them in some fashion. If the text will appear in a
web page, you might want to look for tags that might interfere with the
HTML in the destination page.
If the text is going anywhere near a command shell or script interpreter,
you need to be particularly careful. Far too many people take a backwards
approach, trying to delete "bad" characters. That approach is faulty, as
any bad input that you haven't anticipated will get through. It's better to
assume by default that any input is "bad", and then mark only things that
*exactly* match what you want to allow as "good".
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: 23 Apr 2004 06:54:17 -0700
From: pt1xoom@yahoo.com (Pat)
Subject: Win32::OLE SaveAs Need to force Yes
Message-Id: <7dc17f55.0404230554.15b0a9a9@posting.google.com>
I am having a problem. I want to open 600 excel files and add the
work REV A to the first cell. I am using Win32::OLE. Here is the
code. Very simple.
For every file that opens, I get a box that asks if I want to
overwrite the file. How do I force the answer to the popup to be yes?
#!c:/perl/bin/perl -w
use Win32::OLE;
$workdir = "c:\\temp\\GLNWI";
open (GLN_WI, "$workdir\\gln_file.txt") || die "Can't open gln_file";
@gln_wi = <GLN_WI>;
close GLN_WI;
foreach $file_name (@gln_wi) {
chomp $file_name;
$file_name = $workdir . "\\" . $file_name;
print "file_name = $file_name\n";
$excel = new Win32::OLE ('Excel.Application', 'Quit');
$excel->{Visible} = 0;
$excel->Workbooks->Open("$file_name") or die ("Error: unable to
open document ", Win32::OLE->LastError());
$excel->Range("A1")->{Value} = "Rev A";
$excel->SaveAs('$file_name');
undef $excel;
}
------------------------------
Date: 23 Apr 2004 14:35:21 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude>
Subject: Re: Win32::OLE SaveAs Need to force Yes
Message-Id: <Xns94D46BB8E12F6asu1cornelledu@132.236.56.8>
pt1xoom@yahoo.com (Pat) wrote in news:7dc17f55.0404230554.15b0a9a9
@posting.google.com:
> I am having a problem. I want to open 600 excel files and add the
> work REV A to the first cell. I am using Win32::OLE. Here is the
> code. Very simple.
> For every file that opens, I get a box that asks if I want to
> overwrite the file. How do I force the answer to the popup to be yes?
>
> #!c:/perl/bin/perl -w
use strict;
use warnings # prefer this over -w
>
> use Win32::OLE;
> $workdir = "c:\\temp\\GLNWI";
my $workdir = 'c:/temp/GLNWI';
...
> for my $file_name (@gln_wi) {
> chomp $file_name;
> $file_name = "$workdir/$file_name";
> print "file_name = $file_name\n";
> $excel = new Win32::OLE ('Excel.Application', 'Quit');
# get already active Excelapplication or open new
my $excel = Win32::OLE->GetActiveObject('Excel.Application')
|| Win32::OLE->new('Excel.Application', 'Quit');
> $excel->{Visible} = 0;
> $excel->Workbooks->Open("$file_name") or die ("Error: unable to
> open document ", Win32::OLE->LastError());
> $excel->Range("A1")->{Value} = "Rev A";
> $excel->SaveAs('$file_name');
I don't think you want to use single quotes there.
Instead of using SaveAs, you might want to close the workbook with the
SaveChanges flag set:
$excel->Close(1);
> undef $excel;
Very unnecessary.
--
A. Sinan Unur
1usa@llenroc.ude (reverse each component for email address)
------------------------------
Date: 23 Apr 2004 15:01:07 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude>
Subject: Re: Win32::OLE SaveAs Need to force Yes
Message-Id: <Xns94D470175DEE2asu1cornelledu@132.236.56.8>
"A. Sinan Unur" <1usa@llenroc.ude> wrote in
news:Xns94D46BB8E12F6asu1cornelledu@132.236.56.8:
> use warnings # prefer this over -w
sorry about the missing ;
--
A. Sinan Unur
1usa@llenroc.ude (reverse each component for email address)
------------------------------
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 6452
***************************************
