[22517] in Perl-Users-Digest
Perl-Users Digest, Issue: 4738 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Mar 21 06:06:07 2003
Date: Fri, 21 Mar 2003 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 Fri, 21 Mar 2003 Volume: 10 Number: 4738
Today's topics:
Re: Data 'thinning' with Perl MySQL (Steve)
Re: doubts on \n (Helgi Briem)
Re: How can I....? (Cyber Scorpion)
Re: How reliable are Net::FTP status codes? <please@no.spam>
Re: How to use Net::FTP - FTP Client class <please@no.spam>
looking for a better way of converting data to sort in <mike_solomon@lineone.net>
Re: new Perl feature request: call into shared libs <nospam-abuse@ilyaz.org>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Problem using CGI.pm and SSL. <please@no.spam>
Re: Why can not convet binary to decimal using oct? <please@no.spam>
Re: with ActivePerl, PPM "search" missing results that (Jay Tilton)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 21 Mar 2003 01:39:08 -0800
From: ineverlookatthis@yahoo.com (Steve)
Subject: Re: Data 'thinning' with Perl MySQL
Message-Id: <f0d57f86.0303210139.22358c69@posting.google.com>
Benjamin Goldberg <goldbb2@earthlink.net> wrote in message news:<3E78FDEB.114F0C95@earthlink.net>...
> Steve wrote:
> >
> > Dear All
> >
> > I have a problem which might be of interest:
> >
> > I have an application based on perl and MySQL that logs data from a
> > series of instruments, logging interval ranges from minutes to hours
> > on different instruments. I don't need to keep it all forever but I
> > need to 'thin' it in a defined way. For example, on data over 1 week
> > old reduce observations to a max of one record per hour per
> > instrument, over two weeks old reduce to 1 per 2 hours etc etc. This
> > would allow me to see recent performance in great detail, provide a
> > historical record and provide an indefinite archive of sample values.
> >
> > I cannot come-up with an algorithm that does this in a remotely
> > elegant way. Either I read everything into an array, thin that and
> > then rewrite it - I don't like that because I worry about the size of
> > the array in future developments, or I repeatedly read the table,
> > delete records, reread the table in a very ugly way - which I presume
> > to have huge overheads. In particularly I don't want a solution that
> > depends on being run only once a day or once a week!
>
> The following code assumes that the data contains a 'date' column, which
> is the time that the record was created, and which when fetched produces
> an integer in seconds since the epoch.
>
> $dbh->{FetchHashKeyName} = 'NAME_lc';
>
> # Sort data cronologically.
> my $get = $dbh->prepare( q[SELECT * FROM table ORDER BY date] );
> $get->execute;
> my @cols = @{ $get->{COLS} };
>
> my $del = $dbh->prepare( q[DELETE FROM table WHERE ]
> . join(" AND ", "$_ = ?", @cols ) );
>
> # Last row examined for a particular instrument type.
> my %coalesce;
>
> my $today = time() % (60 * 60);
>
> while( my $rec = $dbh->fetchrow_hashref ) {
> use integer; # avoid need for int() all over the place.
>
> # how many weeks ago was this record?
> my $recweek = ($today - $rec->{date}) / (60 * 60 * 24 * 7);
>
> # no thinning for records less than a week old.
> next if $recweek < 1;
>
> my $other = $coalesce{$rec->{instrument}} ||= {};
> if( !%$other ) {
> %$other = %$rec;
> next;
> }
>
> my $interval = 60 * 60 * 2 ** $recweek;
>
> my $o_inter = $other->{date} / $interval;
> my $r_inter = $rec->{date} / $interval;
> if( $o_inter == $r_inter ) {
> # delete the more recent of the two.
> $del->execute( @{$rec}{@cols} );
> # or, instead, do:
> # $del->execute( @{$other}{@cols} );
> # %$other = %$rec;
> # , to delete the older of the two.
> } else {
> %$other = %$rec;
> }
> }
>
> [untested]
>
> > This must be a common problem with data gathering programmes but I
> > have not been able to find a solution that lets MySQL do the work.
>
> That's not a perl question :)
>
> Also, keep in mind what Xho (ctcgag@hotmail.com) said -- if you create
> an SQL statement that deletes huge numbers of rows at once, it will lock
> the table for the entire duration of that operation. If anything else
> will be using that table, then such behavior would be impolite.
Thanks for all these suggestions and for indulging a not very perl
question. I may be strange, but I think that code should be 'elegant'!
The data table is presently structured with an instrument_id, a
collection datetime and a reading. Adding an expiry time is not
helpful because I cannot be sure in advance which readings will be
succesfully captured (there are several oportunities for data
collision and loss of signal before each report makes it to the db),
anyway it would significantly increase the record size. The whole scan
has to be retrospective.
The approach above is certainly neater than anything I have come-up
with, but I will have to think about just how it will behave !
Apologies for the time to respond, my route to perl.misc died on me.
Steve
------------------------------
Date: Fri, 21 Mar 2003 10:57:27 GMT
From: helgi@decode.is (Helgi Briem)
Subject: Re: doubts on \n
Message-Id: <3e7aeec8.3625561521@news.cis.dfn.de>
On Thu, 20 Mar 2003 18:15:36 +0000 (UTC), Xavier Noria
<fxn@hashref.com> wrote:
>I am not programming nothing diretly related to that, just
> trying to understand that corner of Perl well.
But linebreaks have nothing whatsoever to do with Perl
and everything to do with operating systems and their
conventions. Perl programmers just encounter it
more often than others because Perl is so easily
portable across platforms. Coincidentally, in the last
year or so I have been teaching C++, Java, Python
and Delphi programmers independendently about the
CR/LF issue as these languages increasingly move into
the multi-platform arena. Every programmer who
ports a program from Windows to Unix or vice versa
eventually bangs their heads against this problem.
They are usually clueless about how to solve it.
For myself, I wish the linefeed were standardised as so
many things have been standardised lately, but I suppose
that's a pipedream for now.
--
Regards, Helgi Briem
helgi DOT briem AT decode DOT is
------------------------------
Date: 21 Mar 2003 01:32:29 -0800
From: cyberscorpion@mail.bg (Cyber Scorpion)
Subject: Re: How can I....?
Message-Id: <38d3b40.0303210132.5f00c680@posting.google.com>
cyberscorpion@mail.bg (Cyber Scorpion) wrote in message news:<38d3b40.0303202118.72f7fae3@posting.google.com>...
> Benjamin Goldberg <goldbb2@earthlink.net> wrote in message news:<3E7A276B.2CF4F288@earthlink.net>...
> > Cyber Scorpion wrote:
> > >
> > > I want to compare 2 strings in case in-sensitive mode, but the strings
> > > contain cyrillic characters (ascii code > 127 and < 255) and the
> > > standart way does not work, i.e. the following code:
> > >
> > > if ($sdata =~ /$rdata/i)
> > > {
> > > ....
> > > }
> > >
> > > doesn't work. How can I do this? Please advice!
> >
> > Convert both strings from ISO8859-5 into perl's native utf8 using either
> > the 'encoding' pragma, or a ":encoding(ISO8859-5)" perlio layer, or
> > subroutines from the Encode (or Encode::compat) module, or Text::IConv.
> >
> > Then, you would do as normal:
> >
> > if( $sdata =~ /^\Q$rdata\E\z/i )
> > or:
> > if( lc($sdata) eq lc($rdata) )
> > or:
> > if( uc($sdata) eq uc($rdata) )
> >
> > Where are $sdata and $rdata coming from? Literal strings? Files? A
> > database? (The answer to this question is to know what module will best
> > suit your needs for conversion).
>
> I will look for the 'encoding' pragma in perl help. $sdata and $rdata
> are coming from .html files (this is a part from a simple search
> engine). $sdata is part of the search string (single word) , $rdata is
> single word from .html file. Thanks for your help!
I found very very strange partial solution of my problem: if I just
encode and then decode to unicode everything goes fine (only with big
performance penalty):
#$sdata = encode_utf8($sdata);
#$sdata = decode_utf8($sdata);
#$rdata = encode_utf8($rdata);
#$rdata = decode_utf8($rdata);
# Now the code bellow works for cyrillic characters!!!
if ($sdata =~ /$rdata/i)
{
...
}
Unfortunately some of the cyrillic strings in the $rdata (from the
.html files) are totaly unusable (something happened while
encoding/decoding) and looks like this - "?? ?????? ?? ?? ????????".
Please HELP me to resolve this! Thank you...
------------------------------
Date: Fri, 21 Mar 2003 08:20:01 +0000
From: Chris Lowth <please@no.spam>
Subject: Re: How reliable are Net::FTP status codes?
Message-Id: <yYzea.43$Sl5.16586@newsfep1-win.server.ntli.net>
Tom Beer wrote:
> If Net::FTP returns a 0 status from the put, can I be 100% sure the
> whole file arrived successfully?
No
The FTP protocol does no check-summing, so if corruption occurs, you wont
know. I also suspect that truncation cant be reliably trapped (say: due to
disk full, etc). Solution - check sum the file yourself locally and
remotely, and compare after the transfer.
Chris
--
My real address is: chris at lowth dot sea oh em
Author of "protector" (http://protector.sourceforge.net)
-- OpenSource (free) e-mail virus protection
------------------------------
Date: Fri, 21 Mar 2003 09:47:05 +0000
From: Chris Lowth <please@no.spam>
Subject: Re: How to use Net::FTP - FTP Client class
Message-Id: <8eBea.92$Pq3.14299@newsfep2-gui>
Joe Kamenar wrote:
> Greetings,
>
> I want to use the following sort of code in one of my scripts:
>
> #!/usr/bin/perl
> print "Content-type: text/html\n\n";
>
> use Net::FTP;
>
> $ftp = Net::FTP->new("ftp.fund.xxxxx.com", Debug => 0);
> $ftp->login("nationuser",'xxxxxx');
> $ftp->cwd("/pub");
> $ftp->get("that.file");
> $ftp->quit;
>
> exit;
> When I run this, I get the following:
>
> Can't call method "login" on an undefined value at C:\Perl\bin\test.pl
> line 7.
>
> Of course, the "xxxxx" string contains the real domain and password I
> am using.
> Must I install the ftp application into the Perl directory? If so,
> where do I get it? All I find on a google search is documentation for
> it, but not the code itself.
Chances are high that the NET::FTP->new( .. ) statement failed for some
reason. Add some error testing to the script (check that $ftp is defined
after the call, and print $@ if not).
Chris
--
My real address is: chris at lowth dot sea oh em
Author of "protector" (http://protector.sourceforge.net)
-- OpenSource (free) e-mail virus protection
------------------------------
Date: Fri, 21 Mar 2003 09:55:40 -0000
From: "Mike Solomon" <mike_solomon@lineone.net>
Subject: looking for a better way of converting data to sort in db
Message-Id: <3e7ae16b$1_2@mk-nntp-2.news.uk.tiscali.com>
I need to create a sortable field in my database that will sort numerically
rather than alphabetically
I could sort it correctly in perl but that is not what I am trying to
acheive.
The data is in several formats and I want to convert it as shown below
Orginal Converted
1 0001
10 0010
10A 0010A
10B 0010B
100 0100
OTHER OTHER
I have wriiten the following script that works but I wondered if there was a
better way of doing it.
Any help will be gratefull received
use strict;
use Mike;
#connect to database
DbConnect;
#get data
my $sql = "SELECT stand FROM exhibitors";
my @results = SqlHash($sql);
for my $ref (@results) {
my $stand_sort = $ref->{stand};
if ($stand_sort !~ /[a-z]/i) {
#convert numeric
$stand_sort = sprintf "%04d" , $stand_sort;
} elsif ($stand_sort =~ /^[0-9]+[a-z]/i ) {
#convert items staring with number and ending with letters
$stand_sort =~ /(^[0-9]+)([A-Z]+$)/;
$stand_sort = sprintf "%04d$2" , "$1"
}
#update database
my $sql = "UPDATE exhibitors SET stand_sort = '$stand_sort' WHERE stand =
'$ref->{stand}' ";
SqlExecute($sql);
}
Thanks
Regards
Mike Solomon
------------------------------
Date: Fri, 21 Mar 2003 09:39:34 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: new Perl feature request: call into shared libs
Message-Id: <b5emkm$2upc$1@agate.berkeley.edu>
[A complimentary Cc of this posting was sent to
Martien Verbruggen
<mgjv@tradingpost.com.au>], who wrote in article <slrnb7kpfs.8eh.mgjv@verbruggen.comdyn.com.au>:
> [F'ups set away from both current groups]
Well, since I do not read c.l.c, this would be a one-way-street.
> > Given that no useful program can be written in limits of ANSI-C, I
> > hardly see why this is relevent to the discussion at hand.
>
> That, of course, is nonsensical without the qualification of what
> _you_ mean by "useful". I have many large slabs of code, some
> libraries
Note that I did not discuss "code", only "programs". Of course one
can write some very useful code in ANSI-C. E.g., I use an equivalent of
long addl(long a, long b) { return a+b; }
almost dayly. ;-)
> and some programs, written in compliance with the ISO C
Did not know that this was possible. I got an impression that it does
not allow I/O.
Yours,
Ilya
------------------------------
Date: Fri, 21 Mar 2003 02:22:08 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <8m6dndL2xustVuejXTWc3Q@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.4 $)
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.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
"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: Fri, 21 Mar 2003 09:43:06 +0000
From: Chris Lowth <please@no.spam>
Subject: Re: Problem using CGI.pm and SSL.
Message-Id: <paBea.90$Pq3.14299@newsfep2-gui>
Tintin wrote:
>
> "Hemant Shah" <shah@typhoon.xnet.com> wrote in message
> news:b5dmfs$3ea$1@flood.xnet.com...
>>
>> Folks,
>>
>> We have apache server installed with SSL support. When I use
>> https://www.mysite.com, it brings up standard apache intro page. So SSL
>> seems to work.
>>
>> I wrote a web page using perl CGI.pm and can display it via
>> http://www.mysite.com/myscript.pl. When I run the same script using
>> https://www.mysite.com/myscript.pl I get server error displayed in the
>> browser. When I looked at the apache error_log, it following message
>>
>> Premature end of script headers: /full/path/to/myscript.pl
>>
>> What am I missing?
>>
>>
>> I have print $q->header; in my script.
>
> This has nothing to do with Perl, although I suspect you may have two
> versions of the script, as it is highly unlikely that the http https
> directory paths are the same.
check the error log - if the script wrote anything to stderr, that's where
you'll see the message.
chris
--
My real address is: chris at lowth dot sea oh em
Author of "protector" (http://protector.sourceforge.net)
-- OpenSource (free) e-mail virus protection
------------------------------
Date: Fri, 21 Mar 2003 08:29:11 +0000
From: Chris Lowth <please@no.spam>
Subject: Re: Why can not convet binary to decimal using oct?
Message-Id: <75Aea.53$Sl5.17595@newsfep1-win.server.ntli.net>
Sisyphus wrote:
>
> "W.J cnqin " <qin@freebsd.lzu.edu.cn> wrote in message
> news:86d6klcqfs.fsf@freebsd.lzu.edu.cn...
>>
>> When I read perldoc , I notice that oct can convert binary or heximal
>> to decimal. I write a simple script to test it. But the result is not
>> what I want. Why?
>>
>> #!/usr/bin/perl -w
>>
>> use strict;
>> my @list= ("0b0011", "0x041");
>>
>> foreach (@list){
>> print oct($_),"\n";
>> }
>>
>> The result is:
>> 0
>> 65
>>
>> Any help is appreciated.
>>
>
> Works fine for me - prints
> 3
> 65
> Is that an actual cut'n'paste of your script ?
>
> Cheers,
> Rob
Is this a version issue? What perl version are you using, and on what
platform (not that the latter point should make any difference)?
Chris
--
My real address is: chris at lowth dot sea oh em
Author of "protector" (http://protector.sourceforge.net)
-- OpenSource (free) e-mail virus protection
------------------------------
Date: Fri, 21 Mar 2003 09:21:31 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: with ActivePerl, PPM "search" missing results that match regular expression?
Message-Id: <3e7ad51c.6529696@news.erols.com>
bennett@peacefire.org (Bennett Haselton) wrote:
: I'm running ActivePerl 5.6.0 with PPM interactive shell (2.1.2). When
: I type
:
: ppm search
:
: I get a whole lot of screenfuls of module names, and if I hit Enter
: enough times and scroll far enough through the list, I can see
: Crypt-SSLeay listed:
[snip...yup, it's there]
: But if I do
:
: ppm search "crypt"
:
: then some of the ones listed above are missing from the results:
[huuuge snip. was all that necessary?]
: Specifically, Crypt-Random, Crypt-SKey, Crypt-SSLeay, and
: Crypt-Serpent (and probably some others; I didn't check all the
: Crypt-* modules) are listed in the first set of results, but not in
: the second set. Why would a search for "crypt" not include those
: modules in the results?
:
: I also tried doing:
: ppm search SSLeay
:
: but that turned up zero results, even though "Crypt-SSLeay" is listed
: in the first set of results above.
Suspect that a bare "search" lists everything in the repository,
whether it can be installed on your system or not. But a non-bare
search will return only items useful to your Perl on your OS.
You can go to ppm.activestate.com if you want to look around. Pulling
down Crypt-SSLeay.zip from the repository of 5.6.x packages, I see
from its PPD that it's built for Solaris. If you're not on a Solaris
box, the right thing for PPM to do is not to present it as a package
available for installation.
------------------------------
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 4738
***************************************
