[23633] in Perl-Users-Digest
Perl-Users Digest, Issue: 5840 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Nov 21 09:05:45 2003
Date: Fri, 21 Nov 2003 06: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 Fri, 21 Nov 2003 Volume: 10 Number: 5840
Today's topics:
Re: comments on JAPH? (Anno Siegel)
Re: Comments on parsing solution. (Anno Siegel)
Re: DES has no destroy.al (Anno Siegel)
Re: fork question (bruno)
Re: fork question <tassilo.parseval@rwth-aachen.de>
Re: fork question <usenet@morrow.me.uk>
Re: fork question (Anno Siegel)
Re: fork question <REMOVEsdnCAPS@comcast.net>
Re: Match and cut regex? (Anno Siegel)
Re: Need some help... (Anno Siegel)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Problem in displaying an HTML page (Ajit)
Re: Problem in displaying an HTML page (Anno Siegel)
Re: Problem in displaying an HTML page <abigail@abigail.nl>
Re: Project Organization (Anno Siegel)
Re: Protecting Source code of a perl script <usenet@morrow.me.uk>
Re: Sendmail Configuration Problem news@roaima.freeserve.co.uk
Re: status of redirecting STDOUT/STDERR to file (Anno Siegel)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 21 Nov 2003 10:47:18 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: comments on JAPH?
Message-Id: <bpkqfm$da3$3@mamenchi.zrz.TU-Berlin.DE>
Thomas Kratz <ThomasKratz@REMOVEwebCAPS.de> wrote in comp.lang.perl.misc:
> 2. I just realized (never thought about it before), that when you paste
> the code to the perl interpreter via STDIN, you won't get anything from
> the DATA filehandle. ...
Have you tried it?
Anno
------------------------------
Date: 21 Nov 2003 10:41:02 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Comments on parsing solution.
Message-Id: <bpkq3u$da3$2@mamenchi.zrz.TU-Berlin.DE>
Eric J. Roode <REMOVEsdnCAPS@comcast.net> wrote in comp.lang.perl.misc:
> -----BEGIN xxx SIGNED MESSAGE-----
> Hash: SHA1
>
> Glenn Jackman <xx087@freenet.carleton.ca> wrote in
> news:slrnbrpr47.cjj.xx087@smeagol.ncf.ca:
>
> > Prabh <Prab_kar@hotmail.com> wrote:
> >
> > #!/usr/local/bin/perl
> > use strict;
> > use warnings;
> >
> > # always check the return value of open()
> > open F, "file" or die "can't open file: $!\n";
> > my %hash;
> > while (<F>) {
> > $hash{(split /:/)[0]} ++;
> > }
> > close F;
> > foreach my $f (sort keys %hash) {
> > print "$hash{$f} lines of info on $f\n";
> > }
>
> Are you golfing, or trying to help? If the latter, perhaps you would be
> so kind as to provide a bit of explanation, instead of just throwing some
> fairly dense code at the novice?
Oh, come on. The OP had this (after reading the file into @arr):
> foreach $line ( @arr ) {
> push(@files,(split(/\:/,$line))[0]) ;
> }
Lose the file slurping and replace @arr with %hash, and you end up
more or less with Eric's code. That's not too much of a step.
Anno
------------------------------
Date: 21 Nov 2003 11:42:39 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: DES has no destroy.al
Message-Id: <bpktnf$k64$1@mamenchi.zrz.TU-Berlin.DE>
Greg G <ggershSNACK@CAKEctc.net> wrote in comp.lang.perl.misc:
>
> I've got some perl code that's using Crypt::CBC in which I'm generating
> a DES key like so:
> my $cipher = Crypt::CBC->new( {'key' => '12345678',
> 'cipher' => 'DES',
> 'iv' => '87654321',
> 'regenerate_key' => 0, # default true
> 'padding' => 'space',
> 'prepend_iv' => 0
> });
>
> Well, at some point, the process falls down.
In what way? Is there no error message?
Your code works for me. Perl 5.8.1, Crypt::CBC 2.08.
> I'm not sure exactly where
> in the perl code this is happening, but truss tells me this:
>
> stat("/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/auto/Crypt/DES/DESTROY.al",
> 0x000C1434) Err#2 ENOENT
> open("/usr/local/lib/perl5/5.00503/sun4-solaris/auto/Crypt/DES/DESTROY.al",
> O_RDONLY) Err#2 ENOENT
> open("/usr/local/lib/perl5/5.00503/auto/Crypt/DES/DESTROY.al", O_RDONLY)
> Err#2 ENOENT
> open("/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/auto/Crypt/DES/DESTROY.al",
> O_RDONLY) Err#2 ENOENT
> open("/usr/local/lib/perl5/site_perl/5.005/auto/Crypt/DES/DESTROY.al",
> O_RDONLY) Err#2 ENOENT
> open("./auto/Crypt/DES/DESTROY.al", O_RDONLY) Err#2 ENOENT
>
> As far as I can tell DES doesn't *have* a DESTROY.al. What does this
That doesn't mean perl can't look for one.
> mean, and how can I fix it? (Yes, it's an old version of perl, I
> realize that. I'd prefer not to upgrade it at this point if I don't
> have to.)
There must be tens or hundreds of failed open()s in the truss trace.
This could be the fatal one, but nothing you have reported backs that
up. What makes you think it is?
Anno
------------------------------
Date: 21 Nov 2003 00:37:04 -0800
From: bskorepa@yahoo.com (bruno)
Subject: Re: fork question
Message-Id: <f542e1ac.0311210037.20abe6ae@posting.google.com>
I just found out, by trial and error, that if I remove the
"substr"-function, the program runs fine. Is it possible, that
"substr" is not thread-safe?
thanks, bruno.
------------------------------
Date: 21 Nov 2003 09:33:15 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: fork question
Message-Id: <bpkm4r$rvv$1@nets3.rz.RWTH-Aachen.DE>
Also sprach bruno:
> I just found out, by trial and error, that if I remove the
> "substr"-function, the program runs fine. Is it possible, that
> "substr" is not thread-safe?
Doubt it, but it's not relevant in your case anyway. fork() creates
processes and not threads. Unlike threads, processes do not share
anything (save for file-descriptors) and therefore thread-safeness or
not is a non-issue for this case.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Fri, 21 Nov 2003 11:54:50 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: fork question
Message-Id: <bpkuea$4q8$2@wisteria.csv.warwick.ac.uk>
tassilo.parseval@post.rwth-aachen.de wrote:
> Also sprach bruno:
>
> > I just found out, by trial and error, that if I remove the
> > "substr"-function, the program runs fine. Is it possible, that
> > "substr" is not thread-safe?
>
> Doubt it, but it's not relevant in your case anyway. fork() creates
> processes and not threads. Unlike threads, processes do not share
> anything (save for file-descriptors) and therefore thread-safeness or
> not is a non-issue for this case.
The OP is on Win2k... fork creates ithreads.
Of course, if substr is not ithread-safe this is a bug in perl.
Ben
--
Like all men in Babylon I have been a proconsul; like all, a slave ... During
one lunar year, I have been declared invisible; I shrieked and was not heard,
I stole my bread and was not decapitated.
~ ben@morrow.me.uk ~ Jorge Luis Borges, 'The Babylon Lottery'
------------------------------
Date: 21 Nov 2003 12:12:40 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: fork question
Message-Id: <bpkvfo$k64$3@mamenchi.zrz.TU-Berlin.DE>
Ben Morrow <usenet@morrow.me.uk> wrote in comp.lang.perl.misc:
>
> tassilo.parseval@post.rwth-aachen.de wrote:
> > Also sprach bruno:
> >
> > > I just found out, by trial and error, that if I remove the
> > > "substr"-function, the program runs fine. Is it possible, that
> > > "substr" is not thread-safe?
> >
> > Doubt it, but it's not relevant in your case anyway. fork() creates
> > processes and not threads. Unlike threads, processes do not share
> > anything (save for file-descriptors) and therefore thread-safeness or
> > not is a non-issue for this case.
>
> The OP is on Win2k... fork creates ithreads.
> Of course, if substr is not ithread-safe this is a bug in perl.
Not that I've heard anything specific, but the lvalue-ness of substr
could conceivably lead to problems. After doing "$part = \ substr(
$str, 10, 3)" changes in $$part propagate to $str and change it indirectly.
It must be a bitch to propagate access restrictions on $str to $$part.
Idly speculating,
Anno
------------------------------
Date: Fri, 21 Nov 2003 06:26:07 -0600
From: "Eric J. Roode" <REMOVEsdnCAPS@comcast.net>
Subject: Re: fork question
Message-Id: <Xns943A4BBD7A3C8sdn.comcast@216.196.97.136>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
bskorepa@yahoo.com (bruno) wrote in
news:f542e1ac.0311202338.15301b6c@posting.google.com:
>> Fork slows programs down more often than it speeds them up.
>
> I know, but for each symbol read from the file the program is getting
> an url from the internet, thats where most of the time goes.
> The program runs a couple of hours, so in this case forking 20 times
> speeds things up by almost a factor 20.
Okay, I can see that.
>> but perhaps you're overloading the system's memory capacity.Why do
>> you read the entire file into an array and loop over it? Is it a
>> large file?
>
> only 40 k, so memory issues should not be a problem
Agreed.
(I'd still recommend reading one line at a time; it's a better practice
in general). :-)
- --
Eric
$_ = reverse sort $ /. r , qw p ekca lre uJ reh
ts p , map $ _. $ " , qw e p h tona e and print
-----BEGIN xxx SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBP74EaWPeouIeTNHoEQKajgCeNdkR5JSEoQmCNEUutz8bD1uwHIcAn1AV
ecbbDYxTziO51lqvnNoEWM/x
=Cx0d
-----END PGP SIGNATURE-----
------------------------------
Date: 21 Nov 2003 12:47:36 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Match and cut regex?
Message-Id: <bpl1h8$k64$4@mamenchi.zrz.TU-Berlin.DE>
Bryan <bryan@akanta.com> wrote in comp.lang.perl.misc:
> If I have a 'cut' phrase:
> my $cut = "ABBCCCD";
>
> and a 'sentence':
> my $sentence = "ALSSDJOOASABBCCCDUUSIIASDLLLPP";
>
> What regex do I use to match the ABBCCCD and then chop off everything
> after it?
TIMTOWTDI indeed, as this thread shows. Lookbehind hasn't been used yet:
s/(?<=ABBCCCD).*//;
Anno
------------------------------
Date: 21 Nov 2003 12:01:42 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Need some help...
Message-Id: <bpkur6$k64$2@mamenchi.zrz.TU-Berlin.DE>
Desmond Coughlan <pasdespam_desmond@zeouane.org> wrote in comp.lang.perl.misc:
> I mean, come on: I _know_ Perl, damnit !!
Few people would claim that without qualification.
Anno
------------------------------
Date: Fri, 21 Nov 2003 02:22:53 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <3rGdnXMZArrAViCi4p2dnA@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: 21 Nov 2003 04:43:29 -0800
From: aniwin1@rediffmail.com (Ajit)
Subject: Problem in displaying an HTML page
Message-Id: <141309f1.0311210443.25c41a0@posting.google.com>
Hello everyone,
I am working on Sqwebmail a web-based mail client developed in C&
Perl in backend & has frontend designed in HTML.
Now the problem is, After performing any "file Read/Write" operation
from C, a next HTML page should be displayed, but what actually
happens is the page is displayed partially. & when I refresh the page
the page appears completely.
Programatically the code for the file manipualation is correct, but
why the HTML page is stucking up is a mystry.
Can any one urgently advise me on this matter.....
------------------------------
Date: 21 Nov 2003 13:06:53 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Problem in displaying an HTML page
Message-Id: <bpl2ld$nmj$1@mamenchi.zrz.TU-Berlin.DE>
Ajit <aniwin1@rediffmail.com> wrote in comp.lang.perl.misc:
> Hello everyone,
>
> I am working on Sqwebmail a web-based mail client developed in C&
> Perl in backend & has frontend designed in HTML.
> Now the problem is, After performing any "file Read/Write" operation
> from C, a next HTML page should be displayed, but what actually
> happens is the page is displayed partially. & when I refresh the page
> the page appears completely.
> Programatically the code for the file manipualation is correct, but
> why the HTML page is stucking up is a mystry.
So you're asking a bunch of Perl programmers why a web page of yours
doesn't display completely on the first try. What makes you think the
problem is Perl related?
> Can any one urgently advise me on this matter.....
Usenet doesn't take general claims to urgency very well. What you
can do to get a fast reply is represent your problem in clear terms,
accompanied by an executable example that demonstrates the problem.
You haven't done that.
Anno
------------------------------
Date: 21 Nov 2003 13:12:30 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: Problem in displaying an HTML page
Message-Id: <slrnbrs3pu.c69.abigail@alexandra.abigail.nl>
Ajit (aniwin1@rediffmail.com) wrote on MMMDCCXXXIV September MCMXCIII in
<URL:news:141309f1.0311210443.25c41a0@posting.google.com>:
== Hello everyone,
==
== I am working on Sqwebmail a web-based mail client developed in C&
== Perl in backend & has frontend designed in HTML.
== Now the problem is, After performing any "file Read/Write" operation
== from C, a next HTML page should be displayed, but what actually
== happens is the page is displayed partially. & when I refresh the page
== the page appears completely.
== Programatically the code for the file manipualation is correct, but
== why the HTML page is stucking up is a mystry.
==
== Can any one urgently advise me on this matter.....
You have a bug on line 17.
Abigail
--
perl -wle 'print "Prime" if (1 x shift) !~ /^1?$|^(11+?)\1+$/'
------------------------------
Date: 21 Nov 2003 13:16:04 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Project Organization
Message-Id: <bpl36k$nmj$2@mamenchi.zrz.TU-Berlin.DE>
Ben Liddicott <ben.liddicott@comodogroup.com> wrote in comp.lang.perl.misc:
> It's rather rude to plonk people publicly. It makes you look like a rude
> person.
>
> I might care, but you do this all the time, and for equally trivial reasons;
> so I don't.
>
> If anyone else wants to plonk, plink or plunk me for top-posting, please do
> so now, but quietly so as not to annoy the other posters.
Your choice. So long.
Anno
------------------------------
Date: Fri, 21 Nov 2003 11:51:36 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: Protecting Source code of a perl script
Message-Id: <bpku88$4q8$1@wisteria.csv.warwick.ac.uk>
"Jürgen Exner" <jurgenex@hotmail.com> wrote:
> ctcgag@hotmail.com wrote:
> > Is the administrator of the application also the administrator of the
> > machine on which the application runs? How can an application be
> > considered secure if you don't trust the person who is in charge of
> > it?
>
> Actually this is a very frequent scenario.
> Or would you trust your personal medical files to the admin of the hospital
> computer?
I would (implicitly) trust him not to look at them unless it was
strictly necessary. Or I would trust the hospital to sack him if he
did.
Ben
--
For the last month, a large number of PSNs in the Arpa[Inter-]net have been
reporting symptoms of congestion ... These reports have been accompanied by an
increasing number of user complaints ... As of June,... the Arpanet contained
47 nodes and 63 links. [ftp://rtfm.mit.edu/pub/arpaprob.txt] * ben@morrow.me.uk
------------------------------
Date: Fri, 21 Nov 2003 09:16:24 +0000
From: news@roaima.freeserve.co.uk
Subject: Re: Sendmail Configuration Problem
Message-Id: <8o1191-1s1.ln1@news.roaima.co.uk>
Gunnar Hjalmarsson <noreply@gunnar.cc> wrote:
> You may also want to ask your ISP why their
> sendmail program or mail server is configured to add that "Sender:"
> header.
Because that's the (arguably) correct behaviour for a mailer when someone
tries to send an email whilst pretending to be someone else. To do that
without having sendmail add the Sender: header you need to be in the
list of "trusted users".
Chris
--
@s=split(//,"Je,\nhn ersloak rcet thuarP");$k=$l=@s;for(;$k;$k--){$i=($i+1)%$l
until$s[$i];$c=$s[$i];print$c;undef$s[$i];$i=($i+(ord$c))%$l}
------------------------------
Date: 21 Nov 2003 09:28:51 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: status of redirecting STDOUT/STDERR to file
Message-Id: <bpklsj$da3$1@mamenchi.zrz.TU-Berlin.DE>
jonathan <ttyp32000@yahoo.com> wrote in comp.lang.perl.misc:
> hey all,
>
> just curious, but if I do the following (after __cut__), does this
> have any repercussions for the 'regular' STDERR, STDOUT handles?
It shouldn't.
Why are you dealing with STDOUT in redirect()? You're not using it in
any way.
> __cut__
> sub redirect
> {
> local(*STDERR);
> local(*STDOUT) = *STDERR;
^^^^^^^^^^^^^^^^^^^^^^^^
This does nothing useful.
> open(STDERR, "> /tmp/logit");
>
> print STDERR "HERE!!!\n";
> print STDERR "HEREA!!!\n";
>
> close(STDERR);
> }
>
> redirect();
>
> print STDERR "HEREB!!!\n";
> print STDOUT "HEREC!!!\n";
Anno
------------------------------
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 5840
***************************************
