[24003] in Perl-Users-Digest
Perl-Users Digest, Issue: 6202 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 2 06:05:49 2004
Date: Tue, 2 Mar 2004 03:05:05 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 2 Mar 2004 Volume: 10 Number: 6202
Today's topics:
Re: (newbie) How do I group a string for repetition cou <gnari@simnet.is>
Re: how die in AUTOLOAD (Jay Tilton)
Re: Newbie Need help with if statement <stevenv@operamail.com>
Re: Opening a unique dat file for each user <gnari@simnet.is>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Problems with <usenet@morrow.me.uk>
Re: Problems with <olczyk2002@yahoo.com>
process communication design (c++ <-> perl) <remove_Hannes.Krueger@uibk.ac.at>
Re: Regexp: look ahead and match (Jay Tilton)
Spreadsheet::WriteExcel <fabio@anti-spam.inet.alpha.pl>
Re: Spreadsheet::WriteExcel <kz15@earthling.net>
Re: using sed from with a perl script (Jack Penarth)
Re: using sed from with a perl script <bik.mido@tiscalinet.it>
Re: using sed from with a perl script <bik.mido@tiscalinet.it>
while loop display of files in a directory (mike)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 2 Mar 2004 08:04:40 -0000
From: "gnari" <gnari@simnet.is>
Subject: Re: (newbie) How do I group a string for repetition count? {m,n}
Message-Id: <c21f4n$kv1$1@news.simnet.is>
"Ben Morrow" <usenet@morrow.me.uk> wrote in message
news:c20fqs$frg$1@wisteria.csv.warwick.ac.uk...
>
> "gnari" <gnari@simnet.is> wrote:
> > "gnari" <gnari@simnet.is> wrote in message
> > >
> > > or maybe you want to read perldoc perlre
> > > in particular the bit about zero-width positive look-behind
assertions.
> > > something like / (?<=turkey shoot).*(turkey shoot)/
> >
> > ditto here: / (?<=turkey shoot).*?(turkey shoot)/
>
> Except that what you actually mean is
>
> / (?<= turkey\ shoot .*? ) turkey\ shoot /x
Exept that I actually do not mean this
>
> which unfortunately doesn't work, so some other method must be
> employed.
which is why I did not suggest it
the OP wanted to capture the second occurence
$_='turkey shoot1lkajslkjalsturkey shoot2sdsdfsdturkey shoot3khkj';
print "[$1:$2]\n" if /(?<=turkey shoot).*?(turkey shoot)(\d)/;
prints
[turkey shoot:2]
so what is the problem ?
gnari
------------------------------
Date: Tue, 02 Mar 2004 06:47:48 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: how die in AUTOLOAD
Message-Id: <40442554.288030909@news.erols.com>
Yuri Shtil <yshtil@cisco.com> wrote:
: So the problem lies somewhere in very large chunk of code that I
: omitted
This is why the best troubleshooting aid is a complete program.
: and as I said it was nor practical to post it here.
Troubleshooting is a process of elimination. You trim chunks of code from
the program while observing its new behavior. If trimming a chunk has no
effect on the problem, leave it out. If it makes the problem go away, put
it back. Repeat the process until you have the bare minimum program that
produces the problem. Post that program.
: Ilya Zacharevitch suggested setting $DB:debugLevel to 5 which made the
: die message magically appear. Obviously there was a way to provide help
: without insulting.
Few of the group's readers possess Ilya's Perl kung-fu that could nail that
problem in one intuitive guess. You got lucky.
: I did not mean to appear obtuse or inflammatory but it ticks me when
: people tell me to shut up without a reason other that I posted
: incomplete code.
But do you see why they would want a complete program?
------------------------------
Date: 02 Mar 2004 05:40:26 -0500
From: Steven Vasilogianis <stevenv@operamail.com>
Subject: Re: Newbie Need help with if statement
Message-Id: <863c8rjzvo.fsf@a21.ada>
"Ed" <elpedro@mindspring.com> writes:
> I need help with the if statement below. What I need instead of three if
> statements is one if and two "or" or something similar. Pseudo code would be
>
> if
> $areacode is blank or
> $exchange is blank or
> $phone is blank
> then
> $er_phone = $er_message
> $er_count = $er_count + 1
Erm, your psuedo-code does not describe what your real code below is
doing.
> if ($areacode eq "") {
> $er_areacode = $er_message;
> $er_count = $er_count + 1
> }
> if ($exchange eq "") {
> $er_exchange = $er_message;
> $er_count = $er_count + 1
> }
> if ($phone eq "") {
> $er_phone = $er_message;
> $er_count = $er_count + 1
> }
So, which is it? Set only $er_phone to $er_message, or set the
corresponding $er_(areacode|exchange|count) to $er_message? If it's
the latter, I think your real code is pretty much as good as it can
get.
HTH,
--
steven vasilogianis
------------------------------
Date: Tue, 2 Mar 2004 07:43:40 -0000
From: "gnari" <gnari@simnet.is>
Subject: Re: Opening a unique dat file for each user
Message-Id: <c21dtb$koc$1@news.simnet.is>
"Regent" <arthur0421@163.com> wrote in message
news:c20u7m$gra$1@mail.cn99.com...
> Greg Klinedinst wrote:
> > On Tue, 02 Mar 2004 00:33:49 +0800, Regent <arthur0421@163.com> wrote:
> >
> >
> >
> >>Thanks really. In fact before being used as part of the filename, $uid
> >>is validated beforehand. So
> >>
> >> $uid = $1 if $uid =~ /(.*)/;
> >>
> >>should be no problem. I tried this, and the script seems sound and safe.
> >>But is there any other potential danger in doing this? I see none at the
> >>moment now.
[snip discussion about untainting]
>
> I mean this: in the same script, $uid firstly goes through -T check, and
> then compared with the array of authenticated user names in a database.
this sounds good. after you have made adequate tests on the variable,
if it allright to untaint it as in the example above. I would keep the
untainting
close to the other checks, to make clear that they are connected, so that
future maintainance doesen't make a security hole. the same arguments
apply for more specific untaint, like
$uid = $1 if $uid =~ m!([^/]*)!;
gnari
------------------------------
Date: Tue, 02 Mar 2004 02:22:13 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <tqednZwu1oGo2dndRVn-ig@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: Tue, 2 Mar 2004 05:07:10 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: Problems with
Message-Id: <c214pu$17t$1@wisteria.csv.warwick.ac.uk>
olczyk2002@yahoo.com wrote:
> Activestate Perl v 5.8.0
> I was trying to compile a Perl extension and kept getting tons of
> errors.
>
> So in debugging i reduced everything to a file of a single line.
>
> #include "win32.h"
>
> I compiled this file with the command line:
> >> cl.exe -IE:/Perl/lib/CORE/ test.c
> cl.exe version is 12.00.8804 (VC++ 6.0 Sp2 ).
> I get a ton of errors, the first of which is:
>
> >>E:/Perl/lib/CORE/win32.h(313) : error C2143: syntax error : missing ')' before '*'
>
> Line 313 of win32.h is
> extern int my_fstat(int fd, Stat_t *sbufptr);
What do you get if you run, from the top-level perl source directory,
cl -nologo -I. -Iwin32 win32/win32.h | perl -ne"print if /extern.*my_fstat/"
(add appropriate -Is to find your VC headers)?
Ben
--
Musica Dei donum optimi, trahit homines, trahit deos. |
Musica truces molit animos, tristesque mentes erigit. | ben@morrow.me.uk
Musica vel ipsas arbores et horridas movet feras. |
------------------------------
Date: Mon, 01 Mar 2004 23:46:14 -0600
From: TLOlczyk <olczyk2002@yahoo.com>
Subject: Re: Problems with
Message-Id: <rs7840p2hqnfs5pe5o5vt98ehof0goea8a@4ax.com>
On Tue, 2 Mar 2004 05:07:10 +0000 (UTC), in comp.lang.perl.misc you
wrote:
>What do you get if you run, from the top-level perl source directory,
>
>cl -nologo -I. -Iwin32 win32/win32.h | perl -ne"print if /extern.*my_fstat/"
>
First I get a bunch of errors. win32.h is in lib/CORE. So I fixed
that. Then it complained wrong file type. So I added -EP
( preprocess file to stdout ).
The final command line was:
>> cl -nologo -I. -Iwin32 -Ilib/CORE -EP lib/CORE/win32.h | perl -ne"print if /extern.*my_my_fstat/"
and it produced two lines:
>>win32.h
>>extern int my_fstat(int fd, Stat_t *sbufptr);
The reply-to email address is olczyk2002@yahoo.com.
This is an address I ignore.
To reply via email, remove 2002 and change yahoo to
interaccess,
**
Thaddeus L. Olczyk, PhD
There is a difference between
*thinking* you know something,
and *knowing* you know something.
------------------------------
Date: Tue, 02 Mar 2004 11:06:41 +0100
From: Hannes <remove_Hannes.Krueger@uibk.ac.at>
Subject: process communication design (c++ <-> perl)
Message-Id: <40445cd0@sia.uibk.ac.at>
Hi,
I'm trying to find a better design for communication between a c++ and a
perl/Tk program (processes running at the same time).
Both processes show some graphical content in a window.
If the perl/Tk process updates the view (by user interaction) the c++
program should do so also (immediately) and vice versa.
The values of some variables have to be exchanged.
Formerly I tried this with an SysV IPC shared memory block, which contains
the value of some variables. The "signal" to the other process to update
was implemented via signals (e.g. SIGUSR2). This works fine for the one
direction (perl->c++) but not for the other way due to some "property" of
safe signal handling (in Perl) and Tk MainLoop (see topics: "Tk +
perl-5.8.0 eat and delays signals" and the recent thread "Toplevel doesn't
update").
While trying to find the best design for such a task a few things should be
considered:
1) The production environment: Perl 5.8, Tk 800.024
2) Preferably the solution should be platform independent
3) and (of cause) fast and safe.
Has anybody a good idea? Or tried something similar with success?
Any ideas are welcome...
Thanks
Hannes
PS: I posted this on comp.lang.perl.tk before, but since its not really
related to perl/Tk I think this is the better place.
------------------------------
Date: Tue, 02 Mar 2004 07:23:06 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: Regexp: look ahead and match
Message-Id: <40442fcd.290712221@news.erols.com>
"Matt Garrish" <matthew.garrish@sympatico.ca> wrote:
: while (my $str = <>) {
: my $lval = 0;
: foreach my $char ($str =~ /(.)/g) {
: my $ordval = ord($char);
: if ($char =~ /[A-Za-z]/) {
: if ($ordval == ($lval + 1)) {
: print chr($lval) . "$char\n";
: }
: }
: $lval = $ordval;
: }
: }
I'm hip on being cautious around any regex patterns labelled as
"experimental" (re:other branch of this thread). That technique is
comparatively bulletproof. The \G regex meta can tighten it up without
corrupting the spirit of the algorithm.
while( $str =~ /([[:alpha:]])/g ) {
my $m = $1;
my $n = chr( ord($m)+1 );
print "$m$n\n" if $str =~ /\G$n/;
}
------------------------------
Date: Tue, 02 Mar 2004 10:50:27 +0100
From: Fabio <fabio@anti-spam.inet.alpha.pl>
Subject: Spreadsheet::WriteExcel
Message-Id: <c21lb5$9c2$3@nemesis.news.tpi.pl>
Hello,
there's a module called Spreadsheet::WriteExcel. It allows me to create
a new worksheet and edit its cells:
my $workbook = Spreadsheet::WriteExcel->new('my.xls');
my $worksheet = $workbook->addworksheet();
$worksheet -> write('A2', 222);
But how can I put some values into the cells of an existing worksheet?
Thanks for any advice.
..:: fabio
------------------------------
Date: Tue, 2 Mar 2004 11:07:35 +0100
From: "kz" <kz15@earthling.net>
Subject: Re: Spreadsheet::WriteExcel
Message-Id: <VaZ0c.1$E%6.482@news.uswest.net>
Zoltan Kandi Product and Application Specialist Tellabs Netherlands BV
Perkinsbaan 11 3439 ND Nieuwegein The Netherlands Phone: +31 30 600 40 75
Fax: +31 30 600 40 90 GSM: +31 651 194 291 Email: Zoltan.Kandi@tellabs.com
"Fabio" <fabio@anti-spam.inet.alpha.pl> wrote in message
news:c21lb5$9c2$3@nemesis.news.tpi.pl...
> Hello,
>
> there's a module called Spreadsheet::WriteExcel. It allows me to create
> a new worksheet and edit its cells:
>
> my $workbook = Spreadsheet::WriteExcel->new('my.xls');
> my $worksheet = $workbook->addworksheet();
> $worksheet -> write('A2', 222);
>
> But how can I put some values into the cells of an existing worksheet?
> Thanks for any advice.
>
> ..:: fabio
>
Excerpt from perldoc spreadsheet::writeexcel:
"... The Spreadsheet::WriteExcel module can be used to CREATE a
cross-platform Excel binary file..."
To modify an existing one you will have to look into Win32::OLE.
Read the docs first at
http://search.cpan.org/~jdb/Win32-OLE-0.17/lib/Win32/OLE.pm
HTH,
Zoltan Kandi, M. Sc.
------------------------------
Date: 2 Mar 2004 00:56:55 -0800
From: jackpenarth@aol.com (Jack Penarth)
Subject: Re: using sed from with a perl script
Message-Id: <f27d1c90.0403020056.7df25c2c@posting.google.com>
fifo <fifo@despammed.com> wrote in message news:<20040228185814.GA3446@fleece>...
> At 2004-02-28 13:03 +0000, fifo wrote:
> >
> > {
> > open my $in, '<', 'file.csv' or die $!;
> > open my $out, '>', 'file.csvnew' or die $!;
> > while (<$in>) {
> > last if eof;
> > print;
>
> Of course that should have been
>
> print $out $_;
>
> > }
> > }
> >
Thanks for all your help guys. As ever I have learned a lot from the group.
Jack
------------------------------
Date: Tue, 02 Mar 2004 10:14:54 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: using sed from with a perl script
Message-Id: <rvh84051scqhiik2mk1vul4ho803chrt60@4ax.com>
On Sat, 28 Feb 2004 13:03:50 +0000, fifo <fifo@despammed.com> wrote:
>> >#!/usr/bin/perl -pi
>> >last if eof
>> >__END__
>>
>> But since we're not in a Perl golf competition, I would tend to count
>> this solution as not reliable since, as you surely know, it works for
>> one file only:
>
>Argh, never even considered calling it with more than one file. In my
>defence, I was thinking in terms of replacing the OP's sed call,
>
> `sed '\$d' file.csv > file.csvnew`
>
>with something like
[code snipped]
Which is perfectly fine. After all I was not really answering the OP's
question myself.
Just thought it may have been worth to point out that the code now
quoted at the top of this post may be considered risky in the sense
that while working as expected with one file as an argument on the cmd
line, may yield unexpected results if more than one is specified,
which is something not completely unreasonable for "this kind of
scripts", IMHO...
>My personal preference is to omit the semicolon at the end of a
>statement that's on its own in a block, but to put semicolons at the end
>of all statements if there are more than one. I was just applying this
>rule to the admittedly unusual case of a script consisting of one
>statement!
Well, there's always 'perldoc perlstyle', but as far as I'm concerned
I omit the semicolon *only* if the entire block is on one line, like
thus:
BEGIN { @ARGV=map glob($_), @ARGV }
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: Tue, 02 Mar 2004 10:14:55 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: using sed from with a perl script
Message-Id: <tfi840dbgfohq685ai27fepsh9l3skmm4e@4ax.com>
On Sat, 28 Feb 2004 18:58:15 +0000, fifo <fifo@despammed.com> wrote:
>Of course that should have been
>
> print $out $_;
Probably you already know, but in case you don't, maybe select() could
be of some interest to you...
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: 2 Mar 2004 02:27:51 -0800
From: s99999999s2003@yahoo.com (mike)
Subject: while loop display of files in a directory
Message-Id: <dfd17ef4.0403020227.18afa562@posting.google.com>
hi
i did a code to show the files in a directory
say
while(<test*.txt>)
{
print ;
}
it will show all the files with beginning with test and ending with .txt
but when i assigned it to a variable like this
$files = "test\*\.txt";
while(<"$files">)
{
print ;
}
it doesn't show the files.
Why is this so?
thanks
------------------------------
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 6202
***************************************
