[26411] in Perl-Users-Digest
Perl-Users Digest, Issue: 8582 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Oct 28 06:05:17 2005
Date: Fri, 28 Oct 2005 03:05:04 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 28 Oct 2005 Volume: 10 Number: 8582
Today's topics:
FAQ 3.20 How can I hide the source for my Perl program? <comdog@pair.com>
OSDC (Melbourne, Australia) open for registrations <jarich-spam@perltraining.com.au>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
search & relplace question <Ashwin@DoNot@Email.com>
Re: search & relplace question <tassilo.von.parseval@rwth-aachen.de>
Re: Timelocal input, post good Date filters (from - to) robic0@yahoo.com
Re: Timelocal input, post good Date filters (from - to) robic0@yahoo.com
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 28 Oct 2005 10:03:00 +0000 (UTC)
From: PerlFAQ Server <comdog@pair.com>
Subject: FAQ 3.20 How can I hide the source for my Perl program?
Message-Id: <djst0k$pnb$1@reader2.panix.com>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.
--------------------------------------------------------------------
3.20: How can I hide the source for my Perl program?
Delete it. :-) Seriously, there are a number of (mostly unsatisfactory)
solutions with varying levels of "security".
First of all, however, you *can't* take away read permission, because
the source code has to be readable in order to be compiled and
interpreted. (That doesn't mean that a CGI script's source is readable
by people on the web, though--only by people with access to the
filesystem.) So you have to leave the permissions at the socially
friendly 0755 level.
Some people regard this as a security problem. If your program does
insecure things and relies on people not knowing how to exploit those
insecurities, it is not secure. It is often possible for someone to
determine the insecure things and exploit them without viewing the
source. Security through obscurity, the name for hiding your bugs
instead of fixing them, is little security indeed.
You can try using encryption via source filters (Starting from Perl 5.8
the Filter::Simple and Filter::Util::Call modules are included in the
standard distribution), but any decent programmer will be able to
decrypt it. You can try using the byte code compiler and interpreter
described below, but the curious might still be able to de-compile it.
You can try using the native-code compiler described below, but crackers
might be able to disassemble it. These pose varying degrees of
difficulty to people wanting to get at your code, but none can
definitively conceal it (true of every language, not just Perl).
It is very easy to recover the source of Perl programs. You simply feed
the program to the perl interpreter and use the modules in the B::
hierarchy. The B::Deparse module should be able to defeat most attempts
to hide source. Again, this is not unique to Perl.
If you're concerned about people profiting from your code, then the
bottom line is that nothing but a restrictive license will give you
legal security. License your software and pepper it with threatening
statements like "This is unpublished proprietary software of XYZ Corp.
Your access to it does not give you permission to use it blah blah
blah." We are not lawyers, of course, so you should see a lawyer if you
want to be sure your license's wording will stand up in court.
--------------------------------------------------------------------
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-2002 Tom Christiansen and Nathan
Torkington, and other contributors as noted. All rights
reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
------------------------------
Date: Fri, 28 Oct 2005 17:23:19 +1000
From: Jacinta Richardson <jarich-spam@perltraining.com.au>
Subject: OSDC (Melbourne, Australia) open for registrations
Message-Id: <bqk8f.3821$96.147503@nasal.pacific.net.au>
Registrations for Australia’s second Open Source Developers’ Conference are now
open. Last year’s conference was a huge hit with 60 high quality talks running
in three streams over three days. If you were not able to join us last year make
sure you don’t miss out this year!
The conference is running from Monday 5th – Wednesday 7th December 2005.
If you register before Sunday 30th October you will receive a conference t-shirt
and a $50 discount.
You can register at http://www.osdc.com.au/registration/index.html
OSDC is a grass roots, YAPC-style conference designed by developers for
developers, covering open source languages, tools, libraries, operating systems,
licences and business models. We’re booking 3 lecture rooms each day for the 3
days to hold a new set 60 different talks.
Talks topics range from the safety of Perl’s Safe.pm, to rapid game development
in Python, to using PHP for unorthodox applications, to utilizing Java’s Groovy
in your next application. We also have talks on conference skills, database
integration, digital forensics, Gumstix and Nagios. You can find the full list
of speakers and talk titles at
http://osdc2005.cgpublisher.com/session_descriptions.html
Because there are so many good talks, you can be certain that there will be
something that interests you in every talk session. Each day will start with a
keynote by our excellent keynote speakers. These include Damian Conway, Jonathan
Oxer, Richard Farnsworth (from the Australian Synchrotron) and Anthony Baxter.
The rest of the day will be filled with up to 5 hours of talks and plentiful
food breaks. Our catering choices should result in you being extraordinarily
well fed throughout the days of the conference.
There will also be several BOFs (yet to be organised), lots of opportunities to
socialise, a semi-formal dinner, a partners’ programme and other usual
conference stuff.
If you have any other questions about what is happening, please don’t hesitate
to ask: osdc-help@osdc.com.au
I hope to see you there!
jarich
------------------------------
Date: 28 Oct 2005 07:22:19 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <4361d1a3$0$1763$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, 28 Oct 2005 08:44:02 GMT
From: "Ashwin" <Ashwin@DoNot@Email.com>
Subject: search & relplace question
Message-Id: <mxl8f.13326$_k2.220162@news2.nokia.com>
Hi,
I am not able to understand why
my @result =map ((s/BBI_DIR/BBI_DIR\\RBI/), @BBY); modifies the @BBY
array,
what I expected was that @result should get updated with replaced lines,
but it only updated with value 1 , which is what search function
returns on success
if I try
my @result =map ((s/BBI_DIR/BBI_DIR\\RBI/,$_), @BBY);
@results and @BBY get the same value , but @result also gets those line
which are replaces appended with 1,
what I need is only @result to get updated
--
------------------------------
Date: Fri, 28 Oct 2005 11:25:28 +0200
From: "Tassilo v. Parseval" <tassilo.von.parseval@rwth-aachen.de>
Subject: Re: search & relplace question
Message-Id: <3se94bFneef8U1@news.dfncis.de>
Also sprach Ashwin:
> I am not able to understand why
> my @result =map ((s/BBI_DIR/BBI_DIR\\RBI/), @BBY); modifies the @BBY
> array,
> what I expected was that @result should get updated with replaced lines,
> but it only updated with value 1 , which is what search function
> returns on success
Precisely.
> if I try
>
> my @result =map ((s/BBI_DIR/BBI_DIR\\RBI/,$_), @BBY);
> @results and @BBY get the same value , but @result also gets those line
> which are replaces appended with 1,
> what I need is only @result to get updated
You can make a copy of $_ in the map block and apply s/// to that. Or
you use List::MoreUtils::apply() (courtesy of Brian McCauley) which is
just like map() only that it wont alter the input elements:
use List::MoreUtils qw/apply/;
my @result = apply { s/BBI_DIR/BBI_DIR\\RBI/ } @BBY;
Tassilo
--
use bigint;
$n=71423350343770280161397026330337371139054411854220053437565440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);
------------------------------
Date: Fri, 28 Oct 2005 00:15:24 -0700
From: robic0@yahoo.com
Subject: Re: Timelocal input, post good Date filters (from - to)
Message-Id: <dtj3m1555vb7fgi8ru76f4i3pqf3goma9d@4ax.com>
On Thu, 27 Oct 2005 08:06:05 -0400, "Matt Garrish"
<matthew.garrish@sympatico.ca> wrote:
>
><robic0@yahoo.com> wrote in message
>news:t72ul1htar3krqf6aiflt9mr96ive71kbn@4ax.com...
>>I get some weird concat warnings on print if enabled so its commented.
>
>They aren't weird errors. You don't check if your match succeeds, so you
>wind up using numbered variables that aren't intialized.
>
>> Post any you have (or make some up).
>> Here's mine ..
>>
>> use strict;
>> #use warnings;
>
>Always a bad idea...
>
>>
>> my @dates = ('2/30/5-7/2005', '2/5', '-3/29.2000', '4-12/05',
>> '-12/01-1/03', '10/2002,8/31/2005', '1/2-asdvf');
>>
>> for (@dates) {
>> my $date = $_;
>
>Why?
>
>foreach my $date (@dates)
>
>> print '-'x40,"\n$date\n";
>> $date =~ /.*/;
>> $date =~
>> /^(?:\/*)([0-9]+)?(?:\/*)([0-9]+)?(?:\/*)([0-9]+)?(?:\/*)([,-]*)(?:\/*)([0-9]+)?(?:\/*)([0-9]+)?(?:\/*)
>> ([0-9]+)?(?:\/*)$/;
>> print "date = ($1)($2)($3)($4)($5)($6)($7)\n";
>
>This is you problem. If you look at your output you'll notice that you're
>getting an equal number of unintiliazed warnings as empty value within
>parentheses. This is not a coincidence. Most people will, at a minimum, test
>if their regular expression even succeeded:
>
>if ($date =~ /longregex/) {
> # do something
>}
>
>else {
> print "Invalid date\n";
>}
>
>> }
>>
>> __DATA__
>>
>
>The above is misleading. __DATA__ signifies that the data that follows is
>used by your program (e.g., somewhere in your code is "while (my $line =
><__DATA__>)"). What follows, however, is your output.
>
>Matt
>
About the __DATA__ thing, I thought it was a flag to ignore below as
comments, but thats where I put the output. Whats the right way
to do it?
Thx
------------------------------
Date: Fri, 28 Oct 2005 00:19:27 -0700
From: robic0@yahoo.com
Subject: Re: Timelocal input, post good Date filters (from - to)
Message-Id: <v5k3m1pm99nuimhjb3snhmuumu0giqo7qd@4ax.com>
On Thu, 27 Oct 2005 08:15:57 -0400, "Matt Garrish"
<matthew.garrish@sympatico.ca> wrote:
>
>"Matt Garrish" <matthew.garrish@sympatico.ca> wrote in message
>news:Io38f.7243$ki7.483571@news20.bellglobal.com...
>>
>> <robic0@yahoo.com> wrote in message
>> news:t72ul1htar3krqf6aiflt9mr96ive71kbn@4ax.com...
>>>I get some weird concat warnings on print if enabled so its commented.
>>
>> They aren't weird errors. You don't check if your match succeeds, so you
>> wind up using numbered variables that aren't intialized.
>>
>
>That's a little misleading, on second look (since you manufactured your
>dates to work). You don't require content in all your captures, so you wind
>up with the unintialized warnings. It's still bad practice not to check, and
>feed data that doesn't match your pattern and you will get the messages for
>the above reason.
>
>Matt
>
Hey Matt,
I don't know what you mean by manufactured dates. Maybe this will
help:
elsif ($_ =~ /^([~\/-]+date$)/ || $_ =~
/^([~\/-]+date:)/) {
if ($1 =~ /~/) {
$hCmdp{'Date'}->[0] = '~'; next;
}
$hCmdp{'Date'}->[0] = undef;
$hVars{'Date'} = '';
$hVars{'date_1'} = -1;
$hVars{'date_2'} = -1;
my $date_err = 0;
if ($_ =~ /^[\/-]+date:(.+)$/) #($_
=~ /^[\/-]+date:([0-9\/,\*-]+)/)
{
my $date = $1;
#print "date = \"$date\"\n";
$hCmdp{'Date'}->[0] = $date;
$hVars{'Date'} = $date;
if ($date =~ /\*/) {
$hCmdp{'Date'}->[0] = '*';
$hVars{'Date'} = '*';
} else {
my @times = ();
# Date format:
# -##/##/## = all up to this
date
# ##/##/##- = all from this
date forward
# ##/##/##,##/##/## =
between these two dates
$date =~ /.*/;
$date =~
/^(?:\/*)([0-9]+)?(?:\/*)([0-9]+)?(?:\/*)([0-9]+)?(?:\/*)([,-]*)(?:\/*)([0-9]+)?(?:\/*)([0-9]+)?(?:\/*)([0-9]+)?(?:\/*)$/;
#print "date =
($1)($2)($3)($4)($5)($6)($7)\n";
if (length($1) == 0 &&
length($5) == 0) {
# error, invalid date
format ...
push (@ArgErrs, ['E',
$LOGINFO, $ERRLOG, '9016', (0,0,0,0), "$date", '', 1,0,1]);
$SHOWUSAGE = 1;
$date_err = 1;
} else {
my ($mo,$day,$yr,$cnt)
= (0,0,0,0);
if (length($1) > 0)
{
$cnt++ if
(length($3));
$cnt++ if
(length($2));
$cnt++ if
(length($1));
if ($cnt ==
3) { $mo=$1; $day=$2; $yr=$3; }
elsif ($cnt ==
2) { $mo=$1; $day=1; $yr=$2; }
elsif ($cnt ==
1) { $mo=1; $day=1; $yr=$1; }
if ($day < 1
|| $day > 31 || $mo < 1 || $mo > 12) {
#
error, date parameter out of range ... use default
push
(@ArgErrs, ['E', $LOGINFO, $ERRLOG, '9014', (0,0,0,0), "$mo/$day/$yr",
'', 1,0,1]);
$SHOWUSAGE = 1; $date_err = 1;
}
else {
# here
all is ok ...
#use
Time::Local 'timelocal';
#my
$time = timelocal($sec,$min,$hour,$mday,$mon-1,$year);
my
$time = 0;
eval
{$time = timelocal(0,0,0,$day,$mo-1,$yr);};
if
($@) {
#print "$@\n";
push (@ArgErrs, ['E', $LOGINFO, $ERRLOG, '9015', (0,0,0,0),
"\[$mo/$day/$yr\] $@", '', 1,0,1]);
$SHOWUSAGE = 1; $date_err = 1;
} else
{
push (@times, $time);
if (length ($5) == 0) {
push (@times, timelocal(0,0,0,1,0,2038)); # 2038, max int seconds
with 32-bit
#push (@times, 2**32 - 1);
}
}
}
}
($mo,$day,$yr,$cnt) =
(0,0,0,0);
if (length($5) > 0)
{
$cnt++ if
(length($7));
$cnt++ if
(length($6));
$cnt++ if
(length($5));
if ($cnt ==
3) { $mo=$5; $day=$6; $yr=$7; }
elsif ($cnt ==
2) { $mo=$5; $day=1; $yr=$6; }
elsif ($cnt ==
1) { $mo=1; $day=1; $yr=$5; }
if ($day < 1
|| $day > 31 || $mo < 1 || $mo > 12) {
#
error, date parameter out of range ... use default
push
(@ArgErrs, ['E', $LOGINFO, $ERRLOG, '9014', (0,0,0,0), "$mo/$day/$yr",
'', 1,0,1]);
$SHOWUSAGE = 1; $date_err = 1;
}
else {
# here
all is ok ...
#use
Time::Local 'timelocal';
#my
$time = timelocal($sec,$min,$hour,$mday,$mon-1,$year);
my
$time = 0;
eval
{$time = timelocal(0,0,0,$day,$mo-1,$yr);};
if
($@) {
#print "$@\n";
push (@ArgErrs, ['E', $LOGINFO, $ERRLOG, '9015', (0,0,0,0),
"\[$mo/$day/$yr\] $@", '', 1,0,1]);
$SHOWUSAGE = 1; $date_err = 1;
} else
{
push (@times, $time);
if (length ($1) == 0) {
push (@times, 86400); # 1,1,1970
}
}
}
}
}
$date =~ /.*/;
if ($date_err) {
$hCmdp{'Date'}->[0] =
undef;
$hVars{'Date'} = '';
$hVars{'date_1'} = -1;
$hVars{'date_2'} = -1;
next;
}
($hVars{'date_1'},
$hVars{'date_2'}) = sort { $a <=> $b } @times if (@times == 2);
}
}
else {
$hCmdp{'Date'}->[0] = '*';
$hVars{'Date'} = '*';
}
#print "date err = $date_err\ncmdp =
$hCmdp{'Date'}->[0]\ndate1 = $hVars{'date_1'}\ndate2 =
$hVars{'date_2'}\n";
#<STDIN>; exit (0);
}
------------------------------
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 8582
***************************************
