[22238] in Perl-Users-Digest
Perl-Users Digest, Issue: 4459 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jan 24 00:06:00 2003
Date: Thu, 23 Jan 2003 21:05:07 -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 Thu, 23 Jan 2003 Volume: 10 Number: 4459
Today's topics:
Changing the context of a code block <eric.anderson@cordata.net>
Re: Changing the context of a code block <uri@stemsystems.com>
Re: commenting out code <REMOVEsdnCAPS@comcast.net>
Re: Converting a string to a valid date.. <krahnj@acm.org>
Re: Dynamically Declaring Variables (Dave Fraleigh)
Re: Dynamically Declaring Variables (Tad McClellan)
Re: identifying web host platform? (Alan Barclay)
Re: Is there a better way to format numbers to use comm <bongie@gmx.net>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Reading French-Accented Data (Dave Fraleigh)
Re: Reading French-Accented Data (Ben Morrow)
Re: STDERR Redirection within script (Tad McClellan)
Re: To extract a specific portion of a text file (Tad McClellan)
Re: unlink() (Jay Tilton)
Re: unlink() <jurgenex@hotmail.com>
Re: unlink() <uri@stemsystems.com>
Re: What does this header mean? <bongie@gmx.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 23 Jan 2003 08:34:15 -0500
From: "Eric Anderson" <eric.anderson@cordata.net>
Subject: Changing the context of a code block
Message-Id: <pan.2003.01.23.13.34.13.89070@cordata.net>
Given the below sample script below, is there anyway I can change
define_func to output "AnotherPackage"?
#!/usr/bin/perl
use strict;
use warnings;
package MyPackage;
sub define_func {
my ( $package, $name, $code ) = @_;
no strict 'refs';
*{$package . '::' . $name} = $code;
use strict 'refs';
}
my $my_code = sub {
print __PACKAGE__, "\n";
};
define_func( 'AnotherPackage', 'MyFunc', $my_code );
AnotherPackage::MyFunc();
------------------------------
Date: Fri, 24 Jan 2003 03:01:25 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Changing the context of a code block
Message-Id: <x7iswfntdn.fsf@mail.sysarch.com>
>>>>> "EA" == Eric Anderson <eric.anderson@cordata.net> writes:
EA> Given the below sample script below, is there anyway I can change
EA> define_func to output "AnotherPackage"?
EA> #!/usr/bin/perl
EA> use strict;
EA> use warnings;
EA> package MyPackage;
EA> sub define_func {
EA> my ( $package, $name, $code ) = @_;
EA> no strict 'refs';
EA> *{$package . '::' . $name} = $code;
EA> use strict 'refs';
EA> }
EA> my $my_code = sub {
EA> print __PACKAGE__, "\n";
EA> };
__PACKAGE__ is replaced with the current package name which is
MyPackage.
if you say package AnotherPackage before it, it will print that package
name.
EA> define_func( 'AnotherPackage', 'MyFunc', $my_code );
EA> AnotherPackage::MyFunc();
to get the dynamic package name use the caller() function.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
----- Stem and Perl Development, Systems Architecture, Design and Coding ----
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
Damian Conway Perl Classes - January 2003 -- http://www.stemsystems.com/class
------------------------------
Date: Thu, 23 Jan 2003 20:07:51 -0600
From: "Eric J. Roode" <REMOVEsdnCAPS@comcast.net>
Subject: Re: commenting out code
Message-Id: <Xns930CD7481A2D8sdn.comcast@216.166.71.239>
mfield <mfield@ernie.botany.ubc.ca> wrote in news:3E306A1D.BB777F53
@ernie.botany.ubc.ca:
> I was wondering if there is an easy way to comment out large sections of
> code in perl (using emacs) without commenting out the lines
> individually. Thanks in advance
>
If you're using cperl-mode (you should be), then it's M-x comment-region.
--
Eric
print scalar reverse sort qw p ekca lre reh
ts uJ p, $/.r, map $_.$", qw e p h tona e;
------------------------------
Date: Fri, 24 Jan 2003 02:14:35 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: Converting a string to a valid date..
Message-Id: <3E30A132.E46E90D7@acm.org>
Jeff D Gleixner wrote:
>
> Not really a fair benchmark on the algorithm, since the speed-up is due to
> %shortmonths being a global in one and always re-created in the original.
I was just using the code that was actually posted by the OP and myself
and _did_ make the point that the assignment should be outside the sub.
> Making it a global in the original code does show the original to be faster and
> making each shortmonths hash (along with the other variables! be sure to use
> "my" in your subroutines/methods) a lexical within each subroutine is, of
> course, slower but also shows the original to be faster.
>
> In the long run, unless you're processing hundreds of thousands of these, it's
> not going to matter.
Too true. :-)
John
--
use Perl;
program
fulfillment
------------------------------
Date: 23 Jan 2003 18:15:04 -0800
From: dave@fraleigh.net (Dave Fraleigh)
Subject: Re: Dynamically Declaring Variables
Message-Id: <22f677f.0301231815.783e4097@posting.google.com>
Thanks - ended up using a hash of arrays of hashes to store the
variable and lookup table contents.
eg:
my @tempArry = (\{eval($theCreateLKHash)}, \{eval($theCreateDSHash)});
$lookupTableHash{$theName} = \@tempArry;
and then in the dereference, since I am just referencing one hash of
the object,
\%{$${\@{$lookupTableHash{$theLookupTable}}[1]}}
Worked great.
At any rate, thanks for the reply. I apologize for asking to "hoard"
the answers but wasn't sure about newsgroup etiquette, and email is
really the fastest way to get me.
Cheers.
------------------------------
Date: Thu, 23 Jan 2003 20:43:39 -0600
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Dynamically Declaring Variables
Message-Id: <slrnb31a2r.cjc.tadmc@magna.augustmail.com>
Dave Fraleigh <dave@fraleigh.net> wrote:
> At any rate, thanks for the reply. I apologize for asking to "hoard"
> the answers but wasn't sure about newsgroup etiquette
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html#item_asking_for_emailed_answers
:-)
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 24 Jan 2003 04:22:00 GMT
From: gorilla@elaine.furryape.com (Alan Barclay)
Subject: Re: identifying web host platform?
Message-Id: <1043382120.373981@elaine.furryape.com>
In article <slrnb2tfn7.76k.tadmc@magna.augustmail.com>,
Tad McClellan <tadmc@augustmail.com> wrote:
>I'm Dan <dg1261@cs-REMOVE_THIS-.com> wrote:
>
>> Some time ago (within the last year or two) I recall tinkering with a way to
>> reveal the host platform and server of a website
>
>> Does this ring a bell with anyone?
>
>
>Install the LWP module, then use the HEAD program:
>
>
> HEAD http://www.perl.org
>
>200 OK
>Connection: close
>Date: Wed, 22 Jan 2003 15:54:11 GMT
>Accept-Ranges: bytes
>Server: Apache/2.0.42 (Unix) DAV/2
>Content-Type: text/html; charset=ISO-8859-1
>Client-Date: Wed, 22 Jan 2003 15:53:51 GMT
>Client-Peer: 209.104.63.56:80
>
Of course, that's only reporting what the server claims to be running,
which isn't necessarily what it's really running.
------------------------------
Date: Fri, 24 Jan 2003 03:59:43 +0100
From: "Harald H.-J. Bongartz" <bongie@gmx.net>
Subject: Re: Is there a better way to format numbers to use commas?
Message-Id: <1060667.KHFe7asQWd@nyoga.dubu.de>
Tad McClellan wrote:
> (from the 5.6.1 version of perlfaq5, modified
> to be bound to $num, the double-reverse method was in there too)
Damn, I knew I had seen that code before. ;-)
(And was a bit puzzled not to see it in the 5.8.0 FAQ. Thanks.)
Ciao,
Harald
--
Harald H.-J. Bongartz <bongie@gmx.net>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Q: Why do programmers always get Christmas and Halloween mixed up?
A: Because DEC 25 = OCT 31
------------------------------
Date: Thu, 23 Jan 2003 20:51:43 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.3 $)
Message-Id: <tFKdnfdXqOCiN62jXTWcpw@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.3 $)
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.
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.perl.com/CPAN-local/authors/Dean_Roehrich/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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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 Jan 2003 18:05:39 -0800
From: dave@fraleigh.net (Dave Fraleigh)
Subject: Reading French-Accented Data
Message-Id: <22f677f.0301231805.249d5b74@posting.google.com>
I'm working on a script that will parse a large amount of data, some
of which MAY include french (or other extended-ascii characters in the
128-150 range). Unfortunately, when reading a character with an ASCII
value beyond the lower-ascii set, it seems to translate the read
character without much rhyme or reason... I'm wondering why.
My script reads files, line by line and dumps the line (temporarily)
into a string variable. I've read on the perllocale functions, but
this script was not designed for use on a *nix system, as the data is
coming from a windows source. As such, (and please correct me if I'm
wrong) I don't think I can use POSIX calls and functions.
I've even tried to do a character substitution on the line as it is
read in:
$line = <INFILE>;
$line =~ s/\Ç/'cedille'/g;
Instead of printing a Ç character, it prints a ╟ character.
but that doesn't seem to work. Does anybody have any suggestions on
handling alternative language data (which is still in the ISO latin1
character set) on a Windows machine?
Much appreciated if you do.
Cheers,
Dave
------------------------------
Date: Fri, 24 Jan 2003 02:26:53 +0000 (UTC)
From: mauzo@mimosa.csv.warwick.ac.uk (Ben Morrow)
Subject: Re: Reading French-Accented Data
Message-Id: <b0q89d$9ju$1@wisteria.csv.warwick.ac.uk>
dave@fraleigh.net (Dave Fraleigh) wrote:
>I'm working on a script that will parse a large amount of data, some
>of which MAY include french (or other extended-ascii characters in the
>128-150 range). Unfortunately, when reading a character with an ASCII
>value beyond the lower-ascii set, it seems to translate the read
>character without much rhyme or reason... I'm wondering why.
>
>My script reads files, line by line and dumps the line (temporarily)
>into a string variable. I've read on the perllocale functions, but
>this script was not designed for use on a *nix system, as the data is
>coming from a windows source. As such, (and please correct me if I'm
>wrong) I don't think I can use POSIX calls and functions.
>
>I've even tried to do a character substitution on the line as it is
>read in:
>
>$line = <INFILE>;
>$line =~ s/\Ç/'cedille'/g;
>
>Instead of printing a Ç character, it prints a ╟ character.
>
>but that doesn't seem to work. Does anybody have any suggestions on
>handling alternative language data (which is still in the ISO latin1
>character set) on a Windows machine?
>
>Much appreciated if you do.
Which version of Perl are you using? 5.8 will need a
binmode FILEHANDLE, ":encoding(iso8859-1)"
or some such before Perl can correctly convert Latin-1 into Unicode.
Also, it's a bad idea to put top-bit-set characters directly in the source,
unless you know what you're doing. In 5.8 you can do it with the encoding
pragma, in 5.6.1 you can (I think) use latin1 by default or utf8 with the utf8
pragma.
Ben
------------------------------
Date: Thu, 23 Jan 2003 20:04:08 -0600
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: STDERR Redirection within script
Message-Id: <slrnb317oo.cg7.tadmc@magna.augustmail.com>
Jeffrey Sawyer <sawyerj@uci.edu> wrote:
> I am trying to redirect the verbose output of a sendmail command to STDERR,
perldoc -q STDERR
How can I capture STDERR from an external command?
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Thu, 23 Jan 2003 20:10:20 -0600
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: To extract a specific portion of a text file
Message-Id: <slrnb3184c.cg7.tadmc@magna.augustmail.com>
John Smith <clearguy02@yahoo.com> wrote:
> I sincerely thank you for all your answers. Your first script is not
> valid for my current situation.
So you are saying that your data has changed for a fifth time?
> I tried your second script (that you have posted in your last message
> today).
It was also it the same post as the first one from two days ago.
I just copied the code a second time.
> When I include spaces just in front of the second or third or
> other vlaues in the first "Test Key" field, then your script gives
> only first line (i.e Requirement Key : test_hello_there) and it
> ignores the rest of the values in the first "Test Key" field.
Well yes, that's because the data _was_ at the same level of
indent then.
If you change how the data looks, then the solution might
also need to be changed.
> I want all the values in the first Test Key.
Errr, yes I've gathered that by now.
> How can I modify your script so that I can see all the values in the
> first "Test Key" field no matter whether we change the white space in
> front of them?
That would depend on what we can key on to identify the end of
the "interesting" part.
That in turn, would depend on what the data following the interesting
lines can be.
What the data following the interesting lines can be keeps changing.
I give up!
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 24 Jan 2003 04:21:04 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: unlink()
Message-Id: <3e30bc21.79459155@news.erols.com>
"codeWarrior" <GPatnude@adelphia.net> wrote:
: > > $STATUS = unlink ('./temp_trail.txt', 'prt0001__out.log.1') || die $!;
:
: GP: True. However --> die is NOT being triggered... He should REALLY be
: using "or die" not "|| die"... I'll put money on it -- If he switches the
: code to "or die" It will probably show him what's wrong....
The only difference that change could make is to the value deposited
in $STATUS, and that would depend on die() being able to return a
value to the program, which is dead by then.
------------------------------
Date: Fri, 24 Jan 2003 04:25:49 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: unlink()
Message-Id: <hf3Y9.2235$A17.252@nwrddc01.gnilink.net>
codeWarrior wrote:
> "Tad McClellan" <tadmc@augustmail.com> wrote in message
>> codeWarrior <GPatnude@adelphia.net> wrote:
>>> On Unix systems -- Peril's unlink will NOT remove files if there is
>>> a symbolic link to it...
>>
>> You are incorrect again.
>
> GP: Oh yeah.... RTFM --> Perl in a Nutshell First Edition. Page 137.
Dump that book as fast as possible. How could Perl and/or unlink know, that
there is a softlink pointing to a directory entry (symlinks never point to
files)? This information is not stored by any common file system and it
cannot even be computed reliably because the source of the symlink may be
offline temporarily due to an umounted FS, or NFS, or ....
>> unlink() most certainly will remove files that are targets of
>> symlinks (thereby "breaking" the symlink).
> GP: Oh yeah.... RTFM --> Perl in a Nutshell First Edition. Page 137.
As I said: dump that piece of trash.
However Tad was a bit sloppy in his terminology. Unlink does not remove
files. Instead it removes directories entries. If and how this results in
the actual removal of a file is determinded by the OS and out of Perl's
control.
>>> Are you positive that the file handles are closed at this point in
>>> your scripts ? (Perl normally closes any open file handles when the
>>> script terminates or exits normally...)
>> Filehandles have nothing to do with it either.
>
> GP: Come on smart guy... try unlinking a file you opened for writing
> but never closed...
So what? unlink will happily remove the directory entry for that file. But
because there is still an open link (from your handle) the file will
continue to exist. Doesn't have to be for write, BTW. Same applies to a file
opened for reading, too
And as soon as this handle is closed (which happens at the end of the
program automatically) the link count will be decremented and if it happens
to hit zero the OS will remove the file.
You don't seem to get how file handling works on a FS level, do you?
jue
------------------------------
Date: Fri, 24 Jan 2003 04:41:09 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: unlink()
Message-Id: <x7y95bma6z.fsf@mail.sysarch.com>
>>>>> "c" == codeWarrior <GPatnude@adelphia.net> writes:
>>
>> > On Unix systems -- Peril's unlink will NOT remove files if there is a
>> > symbolic link to it...
>>
>> You are incorrect again.
c> GP: Oh yeah.... RTFM --> Perl in a Nutshell First Edition. Page 137.
>>
>> unlink() most certainly will remove files that are targets of
>> symlinks (thereby "breaking" the symlink).
>>
>>
c> GP: Oh yeah.... RTFM --> Perl in a Nutshell First Edition. Page 137.
i just dug out my copy and nowhere does it say what you claim it
does. in fact it doesn't even mention symlinks which the perl doc for
unlink does.
so your claim is wrong on two fronts - the bit about unlink and symlinks
counting towards the link count and the reference to the nutshell page
which never mentions symlinks.
so now you really should apologize to tad (as i said in another post)
since you are not only claiming wrong facts about unlink, but your
source wasn't quoted properly (and obviously misunderstood by you).
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
----- Stem and Perl Development, Systems Architecture, Design and Coding ----
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
Damian Conway Perl Classes - January 2003 -- http://www.stemsystems.com/class
------------------------------
Date: Thu, 23 Jan 2003 20:09:15 CST
From: "Harald H.-J. Bongartz" <bongie@gmx.net>
Subject: Re: What does this header mean?
Message-Id: <1325519.8MmUuM5RFJ@nyoga.dubu.de>
Brett wrote:
> I solved the problem by unlinking the exe to Perl
Perl runs Perl scripts, not exe files.
> I do have this problem:
[Count.exe expecting a HTTP_REFERER]
Just a guess:
The supposed mode of operation for Count.exe is to be included as an
image link within a HTML page. This page will be the referrer for
Count.exe.
Create an HTML file like this:
,---------- foobar.htm ----------
<html>
<head><title>Counter Test</title></head>
<body>
<p>This page has been called <img src="/cgi-bin/Count.exe"> times.
</p>
</body>
</html>
`--------------------------------
Save it as C:\Inetpub\domain.com\foobar.htm and call it from your
browser (supposedly with http://localhost/foobar.htm).
Then you should see the counter image.
This has, of course, nothing at all to do with Perl, so subsequent
questions should be placed in comp.infosystems.www.authoring.cgi.
X-Post & F'up2 comp.infosystems.www.authoring.cgi set.
Ciao,
Harald
--
Harald H.-J. Bongartz <bongie@gmx.net>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Interesting Error Messages #18:
Backup not found: A)bort, R)etry, M)assive heart failure?
--
PLEASE NOTE: comp.infosystems.www.authoring.cgi is a
SELF-MODERATED newsgroup. aa.net and boutell.com are
NOT the originators of the articles and are NOT responsible
for their content.
HOW TO POST to comp.infosystems.www.authoring.cgi:
http://www.thinkspot.net/ciwac/howtopost.html
------------------------------
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.
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 4459
***************************************
