[13315] in Perl-Users-Digest
Perl-Users Digest, Issue: 725 Volume: 9
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Sep 6 21:07:23 1999
Date: Mon, 6 Sep 1999 17:05:09 -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 Mon, 6 Sep 1999 Volume: 9 Number: 725
Today's topics:
Re: A nice tough RegEx for u to solve..? (Kai Henningsen)
Re: advise please with input buffering and flock proble (Larry Rosler)
Re: Case insensitive SQL query (Kai Henningsen)
Re: Case insensitive SQL query (Kai Henningsen)
CGI programmer wanted <jason@ZZZwickedmoon.co.uk>
Re: DB_File cause my scripts to run slower? (Kai Henningsen)
Re: Desperately searching for perl lint (Kai Henningsen)
Re: Desperately searching for perl lint (Kai Henningsen)
Re: editing images with perl <kims@emmerce.com.au>
Re: essentially; making a long file name into a 8.3 fil (Kai Henningsen)
Re: File listing (Kai Henningsen)
Re: File listing <tchrist@mox.perl.com>
Re: fork? <dan@tuatha.sidhe.org>
Re: FormMail problem recognizing <form name> attribute (Kai Henningsen)
Re: Hopefully on-topic CGI question: simple db routine (Larry Rosler)
Re: Images (Kai Henningsen)
Re: mysql interview (Abigail)
Re: Perl a Black Sheep? (Kai Henningsen)
Re: Perl don't stop (Kai Henningsen)
Re: Perl on VMS? <dan@tuatha.sidhe.org>
Re: Perl5 sendmail (Kai Henningsen)
Re: Programming Question.. List/Email functions (Kai Henningsen)
Re: Sendmail fading away? (was Re: Perl5 sendmail) (Kai Henningsen)
Re: unicode and perl (Kai Henningsen)
Re: using code written in C (anyone know about stemming <dan@tuatha.sidhe.org>
Re: using code written in C (anyone know about stemming (Bill Moseley)
Digest Administrivia (Last modified: 1 Jul 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 06 Sep 1999 21:02:00 +0200
From: kaih=7ONAL3Kmw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: A nice tough RegEx for u to solve..?
Message-Id: <7ONAL3Kmw-B@khms.westfalen.de>
jpeterson@office.colt.net (Jon Peterson) wrote on 26.08.99 in <QHcx3.15$RY.383@news.colt.net>:
> Abigail <abigail@delanet.com> wrote:
> > Jeopardy style and random line breaks... don't expect an answer.
>
> The above line should read:
> "Jeopardy style and random line breaks... don't expect a constructive
> answer"
>
> Otherwise it's a self contradiction.
Not every reply is an answer.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: Mon, 6 Sep 1999 16:02:16 -0700
From: lr@hpl.hp.com (Larry Rosler)
Subject: Re: advise please with input buffering and flock problem
Message-Id: <MPG.123de7c3230298ac989f1c@nntp.hpl.hp.com>
In article <936651329.14643.0.pluto.d4ee06f0@news.demon.nl> on Mon, 6
Sep 1999 23:00:13 +0200, Peter van Tienderen <peter@tienderen.demon.nl>
says...
...
> open(DUB, "+<$dubfile") || die "Content-type: text/plain\n\n Could not open
> $dubfile\n";
> flock(DUB,2) || die "Content-type: text/plain\n\n Could not lock
> $dubfile\n";
> $line = <DUB>;
> # do something with $line here producing $newmessage....
> print DUB $newmessage;
> close DUB;
>
> It seems that when two instances of the script run at the same time, one
> waits nicely at the flock but after that still reads the _old_ contents of
> the DUB file rather the new contents that was just written to it by the
> other instance. Am I right that this can happen, for instance because the
> open automatically loads some contents of the file in an inputbuffer? If so,
> what is a solution?
Your conjecture about the problem seems wrong. You are writing the new
data at the end of the file, not over the original data. So the second
process is reading the original first line, which is still there.
seek DUB, 0, 0 or die ...
after the read and before the write. You might also want to truncate
the file to zero length after the seek, in case the new record is
shorter than the old one.
--
(Just Another Larry) Rosler
Hewlett-Packard Laboratories
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: 06 Sep 1999 20:19:00 +0200
From: kaih=7ONAJNemw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Case insensitive SQL query
Message-Id: <7ONAJNemw-B@khms.westfalen.de>
mrbog@my-deja.com wrote on 03.09.99 in <7qpbv1$l6$1@nnrp1.deja.com>:
> Wow, you're right Lauren, I made a wrong turn and ended up in the wrong
> newsgroup. I though this was comp.lang.perl.misc, not
> alt.rules.fascist.nazi.
True.
> I would think you'd save your feather ruffling for someone who posts
> something REALLY bad,
Oh, you mean like ask a completely off-topic question?
Or maybe like unnecessarily quoting everything?
Or putting the answer *before* the quoted stuff?
Seems she did all that.
> not an innocent question like mine
You didn't ask any innocent question.
There's nothing innocent about asking SQL questions in a Perl group when
there's a whole comp.databases.* hierarchy.
Now go play somewhere you're appreciated. That is *not* around here.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 06 Sep 1999 20:24:00 +0200
From: kaih=7ONAKGP1w-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Case insensitive SQL query
Message-Id: <7ONAKGP1w-B@khms.westfalen.de>
mrbog@my-deja.com wrote on 02.09.99 in <7qmtav$81o$1@nnrp1.deja.com>:
> First of all, no, I will NOT conform to "the usenet standard" of
> responding to posts at the bottom. I dissagree with it and luckily I'm
> on the *internet* which is at its fundament, a medium of free speech
> and expression. I happen to dissagree with the standard and I choose to
> respond at the top. If you don't like that, don't read my messages.
Ok. *plonk*. FOAD.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: Tue, 7 Sep 1999 00:16:38 +0100
From: "Jason Brown" <jason@ZZZwickedmoon.co.uk>
Subject: CGI programmer wanted
Message-Id: <7r1icn$vh5$2@news6.svr.pol.co.uk>
I'm looking for someone fluent in CGI programming to work on various
projects (scripts for running guestbooks for example). I am a graphic
designer myself with experience in the games industry and editorial
illustration. I need someone I can work with over time developing my ideas.
They should be based in the UK, and if living in or around Bath even better.
Please write with your rates of pay and samples of work on the net I can
look at.
Jason (Remove ZZZ from email in replies)
--
Send free virtual cards at http://wickedmoon.co.uk/cards
http://wickedmoon.co.uk web design portraits cartoons illustration
------------------------------
Date: 06 Sep 1999 21:39:00 +0200
From: kaih=7ONAM9HHw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: DB_File cause my scripts to run slower?
Message-Id: <7ONAM9HHw-B@khms.westfalen.de>
meowing@banet.net (meow) wrote on 25.08.99 in <871zcr30eh.fsf@slip-32-101-160-55.ma.us.ibm.net>:
> Chaudhry, Asad <vc13stu1@americasm01.nt.com> wrote:
>
> > I'm using DB_File to tie large arrays and hashes. I find that my scripts
> > run slower when I tie my data with DB_File as opposed to using ordinary
> > arrays and hashes within perl.
>
> That's normal. You are now storing data on disk instead of core, and
> that is nearly always going to be a much slower process. The
Interestingly enough, I got programs to actually speed up by using
DB_File. If your hash or array becomes larger than the working set of your
process, it can become *really* slow; DB_File is much better optimized for
working on disk than Perl arrays or hashes in combination with paging - or
at least that's been my experience.
Of course, with small datasets, it's the other way around. So if there is
a way to know in advance, it might be useful to decide about tieing on-the-
fly.
Another thing. Some algorithms are not particularly good for use with
DB_File. Think about what your data actually does, and see if you can't
change to an algorithm that's better adapted - such as not needing to use
"keys %hash" (except in scalar context), for example.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 06 Sep 1999 20:56:00 +0200
From: kaih=7ONAKsc1w-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Desperately searching for perl lint
Message-Id: <7ONAKsc1w-B@khms.westfalen.de>
talexb@tabsoft.on.ca (T. Alex Beamish) wrote on 26.08.99 in <37c4c19f.281564252@news1.on.sympatico.ca>:
> Thank you all .. since the "perl -MO=Lint -Mstrict -w" that Abigail
> suggested didn't work on the Linux platform I'm using, I will see if I
> can write something myself.
It certainly works on Linux. It does, however, need perl 5.005.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 06 Sep 1999 20:56:00 +0200
From: kaih=7ONAKd9Xw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Desperately searching for perl lint
Message-Id: <7ONAKd9Xw-B@khms.westfalen.de>
mjtg@cus.cam.ac.uk (M.J.T. Guy) wrote on 31.08.99 in <7qguiq$2ms$1@pegasus.csx.cam.ac.uk>:
> Ala Qumsieh <aqumsieh@matrox.com> wrote:
> >Yes. But this only works on variables in the symbol table, and not on
> >lexically scoped vars.
> >
> >Witness:
> >
> >% perl -w
> >my $x;
> >__END__
> >% perl -w
> >local $x;
> >__END__
> >Name "main::x" used only once: possible typo at - line 1.
> >
> >
> >It will be nice to be able to check for that. Btw, is this a bug?
>
> Nope. It's entirely deliberate. -w warnings aren't there just to
> harrass innocent programmers - they're there to catch common and/or
> dangerous mistakes.
Well yes, so why doesn't Perl warn about unused my variables?
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: Tue, 7 Sep 1999 09:22:03 +1000
From: "Kim Saunders" <kims@emmerce.com.au>
Subject: Re: editing images with perl
Message-Id: <936660122.82371@draal.apex.net.au>
>Somebody I know is interested in being able to use perl to edit an
>image. I was wondering if this could even be done. Please take a look at
>this site http://198.173.33.250/signs/display.asp?temptype=WE If you
>choose one of the templates you are sent to a form to fill in
>information you would like to have on the sign and then you can preview
>the changes before requesting that the sign be made. I know that site is
>using ASP. But I was wondering if perl could do it. If perl can, is
>there a resource I can read to find out how to do it.
You use ImageMagick (compile install for your OS. Compiling is not pretty),
and then get the PerlMagick module for it (comes with it these days I
think), and bobs your uncle.
Reads and writes all the different formats (if you have the libs and compile
with them), and it's pretty easy to use, but you can do a *hell* of a lot
with it. Also, buy yourself the o'rielly book "Creating Graphics for the Web
with Perl and GNU Software" or words to that effect (shawn p. wallace from
memory) if you're serious, it's got nearly everything you need to know.
KimS
------------------------------
Date: 06 Sep 1999 23:32:00 +0200
From: kaih=7ONANLx1w-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: essentially; making a long file name into a 8.3 filename..
Message-Id: <7ONANLx1w-B@khms.westfalen.de>
wyzelli@yahoo.com (Wyzelli) wrote on 01.09.99 in <U9_y3.9$5e5.3259@vic.nntp.telstra.net>:
> Kin Lum <kin@0011.com> wrote in message news:37CC5E50.5203B937@0011.com...
> >
> > Of course it is not a good practice. But that's not what
> > the original question asked for. If it is good practice,
> > maybe it is not a good practice to rename them to 8.3
> > but to upgrade the old computer.
>
> Sure. That is generally a good option, if you think it is a good idea to
> spend money rather than do it right.
Truncating a filename can hardly qualify as "doing it right", however
intelligent you go about it.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 07 Sep 1999 00:20:00 +0200
From: kaih=7ORAOjimw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: File listing
Message-Id: <7ORAOjimw-B@khms.westfalen.de>
abigail@delanet.com (Abigail) wrote on 31.08.99 in <slrn7smp9v.9pm.abigail@alexandra.delanet.com>:
> meow (meowing@banet.net) wrote on MMCXC September MCMXCIII in
> <URL:news:877lmckhcr.fsf@slip-32-100-243-84.ma.us.ibm.net>:
> {} Rolf Raven <rolf.raven@quantis.nl> wrote:
> {} The "." was probably fine, if what you're looking to scan is the
> {} current dir. The above code thingy wasn't exactly wrong, but it's not
> {} finished. You've got an array of the files in the directory, now it's
> {} time to filter out the ones you want.
> {}
> {} #!/usr/local/bin/perl -w
> {} use strict;
> {}
> {} my $dirtosearch = '.';
> {} my $findwhat = '\.txt$';
> {}
> {} opendir(DIR, $dirtosearch) or die $!;
> {} my @messofiles = grep { /$findwhat/ && -f "$dirtosearch/$_" }
> readdir(DIR); {} closedir(DIR);
>
> The problem with that is that it will return files with names like
> ".foo.txt", which aren't matched by the shell "*.txt" wildcard.
So use $findwhat = '^[^.].*\.txt$'.
> Bullocks. If you don't like <>, use glob(). There is nothing inherently
> wrong about calling external programs; specially not in this case, where
> the obvious Perl alternative is wrong. -T might not at all wanted; if
> the program isn't running on behalf of someone else, do we really care
> about -T?
The "obvious Perl alternative" is certainly *not* wrong. Or at least I'd
claim that the regex I used is pretty much obvious if that's really what
you want to do.
As for glob, that's approximately
my @files = split /\n/, `/bin/sh echo "*.txt"`
- well, I've seen people argue for
my $file = `cat somefile`
too, but that doesn't make me like either one. Why expensively use an
external program when this is a trivial three-line job done in Perl alone?
*And* you are safer against ugly surprises, such as what happens when your
directory contains a file name with a newline in it.
$ touch 'bad
name'
$perl -e'my @n = glob("bad*name"); print scalar @n, "\n";'
2
$
Still like glob?
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 6 Sep 1999 17:50:15 -0700
From: Tom Christiansen <tchrist@mox.perl.com>
Subject: Re: File listing
Message-Id: <37d45337@cs.colorado.edu>
[courtesy cc of this posting mailed to cited author]
In comp.lang.perl.misc,
kaih=7ORAOjimw-B@khms.westfalen.de (Kai Henningsen) writes:
:Still like glob?
Absolutely. And if you don't like it, fix it.
--tom
--
"'My country right or wrong' is like saying, 'My mother drunk or sober.'"
- G. K. Chesterton
------------------------------
Date: Mon, 06 Sep 1999 23:18:18 GMT
From: Dan Sugalski <dan@tuatha.sidhe.org>
Subject: Re: fork?
Message-Id: <_YXA3.359$9v5.3535@news.rdc1.ct.home.com>
meow <meowing@banet.net> wrote:
> Threads. This is much like forking, with automatically shared memory
> (in other words, just what you originally wanted). Perl's threading
> is poorly implemented and documented at the moment, only works on a
> truly random selection of machines (as in, you won't know until you
> actually try it) and requires different programming quirks with each
> Perl release. It can be used for substantial work if you have the
> right magic perl/OS/hardware combination and are willing to sacrifice
> code portability and a bit of sanity, but you're on your own in making
> it work.
Now, now, it's not that bad. Threads work on any system that implements
either the POSIX draft4 or final thread spec, as well as Win32, OS/2, and
(I think) the Next. The implementation's just fine, thanks, though the
docs are definitely lacking at the moment. The only quirks you need to
work around are bugs, and there are fewer of those with each release. 5.6
should see things nicely solid.
There's definitely no portability problems--threaded perl runs the same on
all systems threaded perl builds on. There are issues with vendor's
threading libraries, which is a problem, but those are mostly fixed.
5.6 should deliver a thread implementation that's production-ready.
(And threads are *not* tough to program--they're really a snap. I don't
understand the mental blocks folks have about 'em. OTOH, signals drive me
loopy. To each his own...)
Dan
------------------------------
Date: 06 Sep 1999 23:09:00 +0200
From: kaih=7ONAMcKHw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: FormMail problem recognizing <form name> attribute
Message-Id: <7ONAMcKHw-B@khms.westfalen.de>
gellyfish@gellyfish.com (Jonathan Stowe) wrote on 29.08.99 in <7qb9rr$2mn$1@gellyfish.btinternet.com>:
> if ($email =~ /(@.*@)|(\.\.)|(@\.)|(\.@)|(^\.)/ ||
> This will reject a vast array of perfectly legal and valid addresses -
> for instance ..@gellyfish.com : it is making a false assumption about
> what is valid in the host-specific part of the address which it shouldnt.
Actually, this one is correct: ..@gellyfish.com is *not* a legal email
address.
See RFC 822; you can't have two dots next to each other (or, indeed, a dot
at the beginning or end of the localpart) unless you put it in quotes.
Yes, many people consider this a misfeature of RFC 822. Nevertheless, it's
still like that in the proposed successor RFC (draft-ietf-drums-msg-fmt-
07.txt) for reasons of backwards compatibility.
Of course, the above rule would also reject ".."@gellyfish.com, which *is*
(syntactically) correct.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: Mon, 6 Sep 1999 16:51:35 -0700
From: lr@hpl.hp.com (Larry Rosler)
Subject: Re: Hopefully on-topic CGI question: simple db routine works stand-alone but not as CGI.
Message-Id: <MPG.123df358b225f35d989f1d@nntp.hpl.hp.com>
In article <37d442a6@calwebnnrp> on Mon, 6 Sep 1999 18:39:53 -0400,
Floyd Morrissette <Floyd@NewWebSite.com> says...
> >> > [Mon Sep 6 12:20:42 1999] [error] [client 192.168.0.1] Premature end
> > of script headers:
> /home/cbarry/public_html/cgi-bin/phone-number-database.cgi
> > ndbm store returned -1, errno 13, key "some-guy" at
> > /home/cbarry/public_html/cgi-bin/phone-number-database.cgi line 14.
> >
> >print <<PRINT_END;
> >Content-type: text/html
>
>
> Should be Content-type: text/html\n\n;
That's exactly what he showed:
print <<PRINT_END;
Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
...
Whatever the problem might be, it isn't what you say. Newlines are
newlines whether written out as "\n" or embedded literally into a string
or a 'here-doc'.
--
(Just Another Larry) Rosler
Hewlett-Packard Laboratories
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: 06 Sep 1999 23:26:00 +0200
From: kaih=7ONANCX1w-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Images
Message-Id: <7ONANCX1w-B@khms.westfalen.de>
mgjv@comdyn.com.au (Martien Verbruggen) wrote on 27.08.99 in <KAnx3.480$bJ4.8761@nsw.nnrp.telstra.net>:
> In article <37C55DE0.842A763B@blackhole-designs.com>,
> Jimmy Humphrey <jimmy@blackhole-designs.com> writes:
> > Content-Type: text/plain; charset=us-ascii
>
> Please don't do that.
Hey, that's about the only part of that article that was right. The
multipart/alternative and text/html stuff is what was wrong.
OTOH, multipart/alternative with text/plain and text/html is still
(slightly) better than having *only* the text/html dreck.
>Usenet is a plain text medium. Not a MIME
> circus.
It's not MIME that's wrong, it's what you do with it. Specifically, text/
html on Usenet and in mail, quoted-printable on Usenet, base64-encoding
(or uuencoding) text attachments both on Usenet and in mail are probably
the worst offenders - whereas, for example, charset labelling, or base64-
encoding binaries *in places where binaries are appropriate* (that is NOT
HERE), are very right.
Just like it's ok to slice bread with a knife, and not ok to slice your
neighbour with it.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 6 Sep 1999 18:36:34 -0500
From: abigail@delanet.com (Abigail)
Subject: Re: mysql interview
Message-Id: <slrn7t8k5c.lh1.abigail@alexandra.delanet.com>
George Reese (borg@imaginary.com) wrote on MMCXCVII September MCMXCIII in
<URL:news:WBXA3.309$96.21438@ptah.visi.com>:
\\ Abigail <abigail@delanet.com> wrote:
\\ : George Reese (borg@imaginary.com) wrote on MMCXCVII September MCMXCIII in
\\ : <URL:news:xGQA3.224$96.12158@ptah.visi.com>:
\\ : $$ Abigail <abigail@delanet.com> wrote:
\\ : $$ : George Reese (borg@imaginary.com) wrote on MMCXCVII September MCMXCIII
\\ : $$
\\ : $$ You have no idea who I am and no meaningful experience with anything I
\\ : $$ have done. So how can you possibly make such an observation?
\\
\\ : You are absolutely correct. The code and postings I've seen from you
\\ : the past 6 or 7 years were not at all meaningful.
\\
\\ I doubt you have seen anything of mine except LPC code. And my
It's code, and I've seen enough code to conclude the absense of coding
skills.
\\ postings apparently do not fit in with your petlanguage.
Most of the postings I've read from you didn't deal with Perl. But perhaps
you mean a different language than Perl with "petlanguage"?
\\ : I have no reason to assume that your books will be meaningful.
\\
\\ You are clearly lacking in reasoning ability then.
If it makes you happy to think so, be my guest.
Abigail
--
perl -e 'for (s??4a75737420616e6f74686572205065726c204861636b65720as?;??;??)
{s?(..)s\??qq \?print chr 0x$1 and q ss\??excess}'
-----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==----------
http://www.newsfeeds.com The Largest Usenet Servers in the World!
------== Over 73,000 Newsgroups - Including Dedicated Binaries Servers ==-----
------------------------------
Date: 06 Sep 1999 21:23:00 +0200
From: kaih=7ONALJpXw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Perl a Black Sheep?
Message-Id: <7ONALJpXw-B@khms.westfalen.de>
feral@vaxxine.com (Ron Feral) wrote on 03.09.99 in <37cf6b8a.85457371@news.vaxxine.com>:
> Yes, and to think about Microsoft's own Hotmail.
>
> lynx -dump -head http://www.hotmail.com/
> HTTP/1.1 302 Found
> Server: Apache/1.3.6 (Unix) mod_ssl/2.2.8 SSLeay/0.9.0b
>
> I wonder if they use Perl. ;-)
Why not? They ship a (broken) perl in the NT resource kit, and sponsor a
non-broken one (ActiveState). Why would they not want to use it?
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 06 Sep 1999 21:26:00 +0200
From: kaih=7ONALYlHw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Perl don't stop
Message-Id: <7ONALYlHw-B@khms.westfalen.de>
mgjv@comdyn.com.au (Martien Verbruggen) wrote on 25.08.99 in <7JGw3.2589$hf4.4677@nsw.nnrp.telstra.net>:
> In article <7pu9ka$ff$1@nnrp1.deja.com>,
> cls@quotient.net writes:
> > Hello
> >
> > When I launch a cgi script with my browser and I stop it by closing the
> > browser, perl.exe is always running and takes all the ressources
>
> \begin{offtopic}
>
> 1) You cannot launch a CGI script with your browser
Unless it's lynx. :-)
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: Mon, 06 Sep 1999 23:30:52 GMT
From: Dan Sugalski <dan@tuatha.sidhe.org>
Subject: Re: Perl on VMS?
Message-Id: <M8YA3.361$9v5.3535@news.rdc1.ct.home.com>
In article <37C1997D.E9177971@email.sps.mot.com>,
Mike.G.Garcia@motorola.com wrote:
> Hello,
>
> Does anyone have any experience with Perl running on VMS?
Yep. Plenty.
> I'd like to know if there are any major difference from Perl that runs
> on Unix.
Hmmm. depends on what you're looking at. A few things don't work (no
forking, and signals are a bit of a hack. But, then, they are everywhere),
but 99.9% of your code should work just dandy.
> We are running Perl 5.004, is it available for VMS?
I hope you mean 5.004_05. But yes, the 5.004 series work fine on VMS.
> If we develop a script on the VMS version, would it be portable
> to the Unix version?
As long as you don't use VMS-specific features (like assuming sane 32-bit
return values from child processes, %ENV changes persisting after the perl
program exits, file versioning with -i, or any of the VMS:: modules) you
should be fine.
Dan
------------------------------
Date: 06 Sep 1999 20:09:00 +0200
From: kaih=7ONAJ8d1w-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Perl5 sendmail
Message-Id: <7ONAJ8d1w-B@khms.westfalen.de>
gellyfish@gellyfish.com (Jonathan Stowe) wrote on 02.09.99 in <37ce3b18_1@newsread3.dircon.co.uk>:
> If "CGI-Factory.com is one of the leading CGI programs providers on the web"
> I hate to think what the worst are like ;-{
Is there a script equivalent to CPAN's module stuff? Something one could
contribute sane versions of all these broken CGI scripts to, then try to
make it known to the script kiddies ...
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 06 Sep 1999 22:13:00 +0200
From: kaih=7ONAMPSXw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Programming Question.. List/Email functions
Message-Id: <7ONAMPSXw-B@khms.westfalen.de>
abigail@delanet.com (Abigail) wrote on 26.08.99 in <slrn7s9nfb.lhu.abigail@alexandra.delanet.com>:
> And the original 7th edition of Unix, lava lamps, and UUCP for your mail
> and news?
Hey, don't knock UUCP. It's used a lot over here, and I certainly wouldn't
want to give it up as long as I'm behind a dialup link. (Or even behind a
slow permanent link. Compression is a must-have in that situation.)
Oh, and count the UUCP links in Usenet II or the other hierarchy one of
these days.
Of course, most of those are probably Taylor UUCP over TCP.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 06 Sep 1999 20:05:00 +0200
From: kaih=7ONAIspXw-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: Sendmail fading away? (was Re: Perl5 sendmail)
Message-Id: <7ONAIspXw-B@khms.westfalen.de>
kag@kag.citysource.com (Kenneth Graves) wrote on 02.09.99 in <slrn7sthdb.jj.kag@kag.citysource.com>:
> In article <eBwz3.48$K4.5894@news.shore.net>, Scratchie wrote:
> >Is Sendmail becoming less common than it used to be? What's replacing it?
>
> Postfix, exim, qmail, probably others I'm forgetting.
Zmailer, smail, or in specialized circumstanses ssmtp, are some more.
> Sendmail is still more common that those three combined, but it
> isn't as ubiquitous as when I started programming.
>
> Some of the above put in a symlink to fake the presence of sendmail,
> so that old scripts assuming it would be there still work.
I believe all of them offer some sort of sendmail-compatible interface
under the name of /usr/{lib,sbin}/sendmail. Of course, nobody forces you
to actually install that part, but given how many programs support calling
that ...
> I prefer to use Net::SMTP in my own scripts, but even that assumes
> there is an SMTP server available.
Just about the only case where there isn't, these days, are intermittently
connected single user systems running Windoze, while being offline.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: 06 Sep 1999 23:51:00 +0200
From: kaih=7ONAO071w-B@khms.westfalen.de (Kai Henningsen)
Subject: Re: unicode and perl
Message-Id: <7ONAO071w-B@khms.westfalen.de>
abigail@delanet.com (Abigail) wrote on 29.08.99 in <slrn7shtkt.23d.abigail@alexandra.delanet.com>:
> chris jaffe (goatholl@sonic.net) wrote on MMCLXXXIX September MCMXCIII in
> <URL:news:37C89446.B7E5E997@sonic.net>:
> `` how do I use unicode with perl?
>
>
> Get a developments version, and use UTF8.
Or use one of the Unicode modules from CPAN, which work with non-
development versions of perl.
perl -MCPAN -eshell
and at the prompt
i /unicode/
should show them.
Kai
--
http://www.westfalen.de/private/khms/
"... by God I *KNOW* what this network is for, and you can't have it."
- Russ Allbery (rra@stanford.edu)
------------------------------
Date: Mon, 06 Sep 1999 23:26:05 GMT
From: Dan Sugalski <dan@tuatha.sidhe.org>
Subject: Re: using code written in C (anyone know about stemming?)
Message-Id: <h4YA3.360$9v5.3535@news.rdc1.ct.home.com>
Bill Moseley <moseley@best.com> wrote:
> I have access to the stem.c routine used by the search engine. If I
> want to use that in my perl program is XS the only way to go?
Nope, but it's the best.
> I guess I could compile a separate C program and call it, but I have
> to call it thousands of times each time the program is run.
Ick. Don't go there.
> Am I correct that if I want to use XS I need to re-link perl? And if I
> don't have access to the perl installed then I'd need to build a
> separate version of perl for my use?
No, and no. If your perl is built to allow dynamically linked extensions
(and pretty much all of 'em are at this point) you don't need to relink or
rebuild anything. If you don't have install access to the system perl, you
can even keep the extension in your own private library.
Check out the perlxs, perlxstut, and (if you're brave) the perlguts docs,
and the docs for the lib module.
Dan
------------------------------
Date: Mon, 6 Sep 1999 16:49:24 -0700
From: moseley@best.com (Bill Moseley)
Subject: Re: using code written in C (anyone know about stemming?)
Message-Id: <MPG.123df2e0ef59df0398970d@nntp1.ba.best.com>
The Glauber (theglauber@my-deja.com) seems to say...
> Adding C code to Perl is NOT that hard. Look into the documentation for
> "perlxstut", "perlxs", "ExtUtils::MakeMaker" and "perlguts", in this
> sequence. If you are lucky, "perlxstut" is all you need to know.
Ok, I'm at the perlxstut stage. The examples are not a problem so far.
Example 4 uses a library instead of just including the C code in the .xs
file itself. What I'm unclear on is when I need to use this library
method vs just placing the code in the .xs file?
I started in on perlxs to find the answer, but got a little lost.
Can I just insert the my C function in the .xs file (just include the
entire stemmer.c file, in this case)? Or are there reasons that I
missed in the tutorial that means I need to build a library first?
And I'm a bit confused about argument passing. The routine I'm trying
to build looks like:
int
Stem( word )
char *word; /* in/out: the word stemmed */
So Stem() returns an int, but also modifies word.
It does an explicit return( 1 ) or return( 0 ). Would I need to modify
the code and put in RETVAL = 1 or RETVAL = 0 above those statements, and
then
OUTPUT:
word
RETVAL
To return both values?
This stuff really makes me feel dumb.
Thanks for the help,
--
Bill Moseley mailto:moseley@best.com
pls note the one line sig, not counting this one.
------------------------------
Date: 1 Jul 99 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 1 Jul 99)
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.misc (and this Digest), send your
article to perl-users@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.
The Meta-FAQ, an article containing information about the FAQ, is
available by requesting "send perl-users meta-faq" from
almanac@ruby.oce.orst.edu. The real FAQ, as it appeared last in the
newsgroup, can be retrieved with the request "send perl-users FAQ" from
almanac@ruby.oce.orst.edu. Due to their sizes, neither the Meta-FAQ nor
the FAQ are included in the digest.
The "mini-FAQ", which is an updated version of the Meta-FAQ, is
available by requesting "send perl-users mini-faq" from
almanac@ruby.oce.orst.edu.
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 V9 Issue 725
*************************************
