[25553] in Perl-Users-Digest
Perl-Users Digest, Issue: 7797 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Feb 18 06:05:38 2005
Date: Fri, 18 Feb 2005 03:05:12 -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, 18 Feb 2005 Volume: 10 Number: 7797
Today's topics:
Re: editing pdf files with perl <bart.lateur@pandora.be>
Re: editing pdf files with perl aditya2507@gmail.com
Emacs modules for Perl programming (Jari Aalto+mail.perl)
Re: Feeding false an App (Anno Siegel)
Re: forking & (mysql)sockets arnevt@sloeber.office.xs4all.be
Re: Perl script timeout problem (sipitai)
Re: Perl script timeout problem (sipitai)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Reading compressed file and its conversion to numbe <bart.lateur@pandora.be>
Re: SET Operations in Perl <georgekinley@hotmail.com>
Re: use strict; and O_WRONLY <tassilo.von.parseval@rwth-aachen.de>
Re: use strict; and O_WRONLY <bart.lateur@pandora.be>
Re: Using Perl to Parse Excel File <bart.lateur@pandora.be>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 18 Feb 2005 09:56:09 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: editing pdf files with perl
Message-Id: <toeb115qabk7ob6bthvlqsp7jr6fvlochv@4ax.com>
aditya2507@gmail.com wrote:
>I have a collection of PDF files which are stored in a directory. These
>PDF files follow a particular format. Each one of these files has some
>fields in the first page which are left blank. I need to fill those
>fields based on the input given by the user(s).
>I CANNOT overwrite these PDF files since the data contained in them is
>not elsewhere. I simply need to be able to edit and update the first
>page of these PDF files.
>
>Is there any way I can do this with Perl?
>
The module PDF::Reuse (see CPAN) is more or less made for situations
like this. To avoid disappointments, I'll tell you what it does. It
opens a PDF file, and you can *add* new stuff on top of the old stuff,
draw on it. It *does not* search and replace some template text in your
PDF file. For blank fields, this might just work.
--
Bart.
------------------------------
Date: 17 Feb 2005 21:53:19 -0800
From: aditya2507@gmail.com
Subject: Re: editing pdf files with perl
Message-Id: <1108705999.126907.112770@f14g2000cwb.googlegroups.com>
Hi,
I wish to thank everyone who took time out to read and answer my
doubt(s) here. Ultimately I used PDF::Reuse which served the purpose.
Bill, I visited your website and its a very useful place for people
working in the PDF-Perl Domain.
Thanks again. It has been a learning experience here. :o)
Regards
Aditya Kumar
------------------------------
Date: 18 Feb 2005 05:34:13 GMT
From: <jari.aalto <AT> poboxes.com> (Jari Aalto+mail.perl)
Subject: Emacs modules for Perl programming
Message-Id: <perl-faq/emacs-lisp-modules_1108704832@rtfm.mit.edu>
Archive-name: perl-faq/emacs-lisp-modules
Posting-Frequency: 2 times a month
URL: http://tiny-tools.sourceforge.net/
Maintainer: Jari Aalto A T poboxes com
Announcement: "What Emacs lisp modules can help with programming Perl"
Preface
Emacs is your friend if you have to do anything comcerning software
development: It offers plug-in modules, written in Emacs lisp
(elisp) language, that makes all your programmings wishes come
true. Please introduce yourself to Emacs and your programming era
will get a new light.
Where to find Emacs/XEmacs
o Unix:
http://www.gnu.org/software/emacs/emacs.html
http://www.xemacs.org/
o Unix Windows port (for Unix die-hards):
install http://www.cygwin.com/ which includes native Emacs 21.x.
and XEmacs port
o Pure Native Windows port
http://www.gnu.org/software/emacs/windows/ntemacs.html
ftp://ftp.xemacs.org/pub/xemacs/windows/setup.exe
o More Emacs resources at
http://tiny-tools.sourceforge.net/ => Emacs resource page
Emacs Perl Modules
Cperl -- Perl programming mode
http://www.cpan.org/modules/by-authors/id/ILYAZ/cperl-mode/
http://math.berkeley.edu/~ilya/software/emacs/
by Ilya Zakharevich
CPerl is major mode for editing perl files. Forget the default
`perl-mode' that comes with Emacs, this is much better. Comes
standard in newest Emacs.
TinyPerl -- Perl related utilities
http://tiny-tools.sourceforge.net/
If you ever wonder how to deal with Perl POD pages or how to find
documentation from all perl manpages, this package is for you.
Couple of keystrokes and all the documentaion is in your hands.
o Instant function help: See documentation of `shift', `pop'...
o Show Perl manual pages in *pod* buffer
o Grep through all Perl manpages (.pod)
o Follow POD references e.g. [perlre] to next pod with RETURN
o Coloured pod pages with `font-lock'
o Separate `tiperl-pod-view-mode' for jumping topics and pages
forward and backward in *pod* buffer.
o Update `$VERSION' variable with YYYY.MMDD on save.
o Load source code into Emacs, like Devel::DProf.pm
o Prepare script (version numbering) and Upload it to PAUSE
o Generate autoload STUBS (Devel::SelfStubber) for you
Perl Module (.pm)
TinyIgrep -- Perl Code browsing and easy grepping
[TinyIgrep is included in Tiny Tools Kit]
To grep from all installed Perl modules, define database to
TinyIgrep. There is example file emacs-rc-tinyigrep.el that shows
how to set up dattabases for Perl5, Perl4 whatever you have
installed
TinyIgrep calls Igrep.el to to do the search, You can adjust
recursive grep options, set search case sensitivity, add user grep
options etc.
You can find latest `igrep.el' module at
<http://groups.google.com/groups?group=gnu.emacs.sources> The
maintainer is Jefin Rodgers <kevinr <AT> ihs.com>.
TinyCompile -- To Browse grep results in Emacs *compile* buffer
TinyCompile is a minor mode for *compile* buffer from where
you can collapse unwanted lines or shorten file URLs:
/asd/asd/asd/asd/ads/as/da/sd/as/as/asd/file1:NNN: MATCHED TEXT
/asd/asd/asd/asd/ads/as/da/sd/as/as/asd/file2:NNN: MATCHED TEXT
-->
cd /asd/asd/asd/asd/ads/as/da/sd/as/as/asd/
file1:NNN: MATCHED TEXT
file1:NNN: MATCHED TEXT
End
------------------------------
Date: 18 Feb 2005 10:46:28 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Feeding false an App
Message-Id: <cv4h24$772$1@mamenchi.zrz.TU-Berlin.DE>
Larry <larry_wallet@yahoo.com> wrote in comp.lang.perl.misc:
[...]
> You are very arrogant for someone who is not even published on cpan.
That remark shows your cluelessness.
Publishing on CPAN (not "being published") is about as hard as buying
a book from Amazon -- only cheaper.
Anno
------------------------------
Date: Fri, 18 Feb 2005 10:35:03 +0100
From: arnevt@sloeber.office.xs4all.be
Subject: Re: forking & (mysql)sockets
Message-Id: <pan.2005.02.18.09.35.03.677150@sloeber.office.xs4all.be>
>
> I don't know what a "getcounter" script is, and have no experience with
> Net::SNMP, but I do know that for general databse work, mysql connections
> should be opened after the fork(s), not before.
a "getcounter" script is a script that gets counters :D
i switched to non blocking requests, so i don't have to fork anymore,
problem solved for me :)
arne
------------------------------
Date: 18 Feb 2005 00:53:01 -0800
From: sipitai@hotmail.com (sipitai)
Subject: Re: Perl script timeout problem
Message-Id: <76360ac4.0502180053.7ecbd0ce@posting.google.com>
Brian McCauley wrote...
> I shall assume this is a stealth CGI question.
>
> Also, this does not appear to be a Perl question at all.
>
> Ask yourself this: Would you expect the answer to be any different if
> your CGI script were in python, C, pasacal, bash...?
Maybe, maybe not. I figure this problem could originate from either
the script itself, or the environment its being executed in.
Although if anyone could help me narrow this down I would be greatly
appreciative.
> Do not have the script send the file. Have it perform an internal
> redirect to the file. You may or may not be able to configure your web
> server to prevent people bypassing the script but even if you can't you
> can just make sure that the directory name is obscure.
Unfortunately there are a number of reasons why this wouldnt work, one
of which is that the "key" for the file needs to be able to expire.
Although thanks anyway for the feedback.
------------------------------
Date: 18 Feb 2005 01:04:34 -0800
From: sipitai@hotmail.com (sipitai)
Subject: Re: Perl script timeout problem
Message-Id: <76360ac4.0502180104.57f02c1e@posting.google.com>
Gregory Toomey wrote...
> So fix httpd.conf Why bother us.
>
> # Timeout: The number of seconds before receives and sends time out.
> Timeout 1800
>
> # KeepAlive: Whether or not to allow persistent connections (more than
> # one request per connection). Set to "Off" to deactivate.
> KeepAlive On
I would like to think of that sort of solution as a last resort. I
would prefer to find out why it is timing out in the first place and
then fix the problem.
> Err, why?
Because the Timeout value is there for a reason, and increasing it
just to hide the problem isn't what I would call a solution.
Although thanks anyway for the feedback.
------------------------------
Date: 18 Feb 2005 08:22:17 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <4215a5b8$0$23564$8b463f8a@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.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: Fri, 18 Feb 2005 11:01:13 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: Reading compressed file and its conversion to numbers.
Message-Id: <8hib11tuk6nvo87i6tv5on0ft8pfdnoie9@4ax.com>
Henry Lenzi wrote:
> Is there a way to read it and obtain the ANSI extended charset hexadecimal _numbers_?
> For instance, the above line would display:
>
>3B C2 4F etc...
unpack "H*", $string;
will do it directly, but it won't have those spaces between the bytes.
Oh, and it's in lower case too.
Perhaps try this:
$hex = join " ", map {sprintf "%02X", $_ } unpack 'C*', $string;
You can process the file in chunks at a time.
--
Bart.
------------------------------
Date: Fri, 18 Feb 2005 07:17:59 GMT
From: "George" <georgekinley@hotmail.com>
Subject: Re: SET Operations in Perl
Message-Id: <xn0dyna913ysotx008@news.europe.nokia.com>
Bernard El-Hagin wrote:
> "George" <georgekinley@hotmail.com> wrote:
>
> [...]
>
> >> I think it was a typo. George probably mean SETI Operations.
> >>
> >> I know all about them, but I'm not allowed to talk about them.
> >>
> >>
> >> Abigail
> >
> > If you don't understand difference between SET Operations and
> > SETI's Operation , you are sure dumb head, and if someone asks for
> > SETI in Science group dick head like you will again complain about
> > typo "he mean SET"
>
>
> Is he a "dumb head" or a "dick head"? You seem to be torn.
>
> Oh well, it doesn't matter anyway.
>
>
> *plonk*
does it make you feel any better
------------------------------
Date: Fri, 18 Feb 2005 07:47:11 +0100
From: "Tassilo v. Parseval" <tassilo.von.parseval@rwth-aachen.de>
Subject: Re: use strict; and O_WRONLY
Message-Id: <slrnd1b3rf.pi.tassilo.von.parseval@localhost.localdomain>
Also sprach Sherm Pendley:
> Gunnar Hjalmarsson wrote:
>
>> Hmm.. I did look in the Fcntl POD, which talks about constants. Is that
>> POD possibly outdated?
>
> I think I might have been wrong. The AUTOLOAD in Fcntl.pm calls a C
> constant() function that's defined in XS code. I'm not too certain what
> const-c.inc and const-xs.inc do - they're convoluted, to say the least.
const-xs.inc is the XS implementation of the 'constant' function as
available from AUTOLOAD. 'XS_constant' then calls the C function
'constant' (defined in const-c.inc). This one then works a bit like a
finite state machine that does pattern matching on the name of the
requested constant. This matching happens in those huge switch/case
statements that checks whether an accepting or rejecting state is
reached. It will then return the appropriate value (either the constant
or an error).
I never quite understood why a simple
if (memEQ(name, "CONST1", 6)) {
#ifdef CONST1
return newSViv(CONST1);
#else
return &PL_sv_undef;
#endif
}
isn't both easier and faster than those switch/case statements.
Tassilo
--
use bigint;
$n=71423350343770280161397026330337371139054411854220053437565440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);
------------------------------
Date: Fri, 18 Feb 2005 10:52:03 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: use strict; and O_WRONLY
Message-Id: <06ib11ltnio0vr2cdmeaovc8pi5deqjapi@4ax.com>
Brian McCauley wrote:
>Your problem is that you are trying to use the O_WRONLY function without
>first defining it. All strict does is make perl tell you about your
>mistake rather than silently treat it as the string 'O_WRONLY' (which
>won't work).
Makes one wonder if that really shouldn't have been spelled "O_WRONGLY".
:)
--
Bart.
------------------------------
Date: Fri, 18 Feb 2005 10:05:47 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: Using Perl to Parse Excel File
Message-Id: <l7fb111u1157m6e4uaqoc0go1617bqbd79@4ax.com>
mull0024@juno.com wrote:
>I'm using Perl to parse through an Excel file and I'm having trouble
>with a date field. The date displays as 1-Jan-63 (for example) but
>when the script runs it is printing as
>"Win32::OLE::Variant=SCALAR(0x2626704)" If I print it using two $
>signs then Perl prints it as "39047808"
>2) How do I get the data from Excel to print in Perl as dd/mm/yy ?
See if you can invoke a function with a name like "formatted", to make
Excel convert the internal format to displayed text format. Start
looking in the docs for Win32::OLE::Variant, as that is the kind of
object you're seeing here. Docs on CPAN:
<http://search.cpan.org/~jdb/libwin32-0.24/OLE/lib/Win32/OLE/Variant.pm>
Oh, look at that, there's a Date() method:
Date([FORMAT[, LCID]])
Converts the VARIANT into a formatted date string.
--
Bart.
------------------------------
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 7797
***************************************
