[23191] in Perl-Users-Digest
Perl-Users Digest, Issue: 5412 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Aug 23 00:05:50 2003
Date: Fri, 22 Aug 2003 21:05:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 22 Aug 2003 Volume: 10 Number: 5412
Today's topics:
Commonly used modules <jonov@iprimus.com.au>
Re: Commonly used modules <simon@unisolve.com.au>
Re: Commonly used modules <tim@vegeta.ath.cx>
Re: File transfers <bwalton@rochester.rr.com>
Re: operator in a variable? <uri@stemsystems.com>
Perl build script woes doing Source Safe get (Marc S. Gibian)
Problem with split function (David Morel)
Re: Problem with split function <simon@unisolve.com.au>
Re: Problem with split function <Nekid@jaybird.com>
Re: Pure Perl SQL server <bwalton@rochester.rr.com>
Re: Pure Perl SQL server <newsfeed@boog.co.uk>
Re: stemming algotithms in perl <bwalton@rochester.rr.com>
Re: Text::Autoformat and 'psychosis' <usenet@dwall.fastmail.fm>
Re: What ever happened to comp.lang.perl ? <islaw@adexec.com>
Re: What ever happened to comp.lang.perl ? <flavell@mail.cern.ch>
Re: What ever happened to comp.lang.perl ? <tcurrey@no.no.no.i.said.no>
Re: What ever happened to comp.lang.perl ? <luriel@gfy.yahoo.com>
Re: What ever happened to comp.lang.perl ? <noreply@gunnar.cc>
Re: What ever happened to comp.lang.perl ? <matthew.garrish@sympatico.ca>
Re: What ever happened to comp.lang.perl ? <jurgenex@hotmail.com>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 23 Aug 2003 12:49:08 +1000
From: Jon <jonov@iprimus.com.au>
Subject: Commonly used modules
Message-Id: <3f46d58a_1@news.iprimus.com.au>
Hi,
I'm curious to know what CPAN modules people use in their general day-to-day
perl scripting (or can't live without). For example I make lots of use of
the Date::Manip module and would hate to have to ever implement something
like that.
Jon.
------------------------------
Date: Sat, 23 Aug 2003 12:54:10 +1000
From: Simon Taylor <simon@unisolve.com.au>
Subject: Re: Commonly used modules
Message-Id: <bi6l3i$282u$1@otis.netspace.net.au>
Jon wrote:
> Hi,
>
> I'm curious to know what CPAN modules people use in their general day-to-day
> perl scripting (or can't live without). For example I make lots of use of
> the Date::Manip module and would hate to have to ever implement something
> like that.
>
> Jon.
>
Here are some in no particular order:
CGI
CGI::Carp 'fatalsToBrowser';
Date::Manip (I agree, it's fabulous)
Date::Calc
Tk
Getopt::Declare
Mime::Lite
DBI
Sys::Hostname
XML::Parser
Net::FTP
Text::ParseWords
SOAP::Lite
Data::Dumper
And of course Apache::* for mod_perl
Hope this helps,
Simon Taylor
------------------------------
Date: 22 Aug 2003 20:23:30 -0700
From: Tim Hammerquist <tim@vegeta.ath.cx>
Subject: Re: Commonly used modules
Message-Id: <slrnbkdnin.4v9.tim@vegeta.ath.cx>
Jon graced us by uttering:
> I'm curious to know what CPAN modules people use in their
> general day-to-day perl scripting (or can't live without). For
> example I make lots of use of the Date::Manip module and would
> hate to have to ever implement something like that.
Some of my must-haves:
Apache::ASP
CGI
CGI::Carp
File::Find
Getopt::Std
My US$0.02,
Tim Hammerquist
--
Appreciation is a wonderful thing:
It makes what is excellent in others belong to us as well.
-- Voltaire
------------------------------
Date: Sat, 23 Aug 2003 02:11:33 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re: File transfers
Message-Id: <3F46CD31.40404@rochester.rr.com>
SRam wrote:
> What is the limit of syswrite function. How can I convert an image
> from binary mode so as to store it in a buffer and send it to client
> and the client has to again decode the same to display the image
>
Have you considered FTP (File Transfer Protocol)? You can do it from
perl if you
use Net::FTP;
That is all set up, clients and servers are built-in or available for
most any platform, and you don't have to mess around with syswrite or
any low-level protocol/socket/etc stuff at all. Be sure to use FTP in
its "binary" mode if you are transmitting an image between two different
types of machines (*nix <-> Windoze, for example).
--
Bob Walton
------------------------------
Date: Sat, 23 Aug 2003 00:43:34 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: operator in a variable?
Message-Id: <x7wud5nqyx.fsf@mail.sysarch.com>
>>>>> "ES" == Eric Schwartz <emschwar@pobox.com> writes:
ES> Uri Guttman <uri@stemsystems.com> writes:
>>>>>>> "MPB" == Michael P Broida <michael.p.broida@boeing.com> writes:
MPB> Combine that with someone's prior suggestion involving
MPB> using functions for the operators. Put the FUNCTION NAME
MPB> in your "Op" entry and call that function to perform the
MPB> operation needed.
>>
>> and that is getting back to symrefs which are bad.
ES> A way of doing the same thing that doesn't require symrefs is to use
ES> a hash of subrefs:
ES> my %funcHs = ( '+' => sub { $_[0] + $_[1] },
ES> '-' => sub { $_[0] - $_[1] },
ES> '*' => sub { $_[0] * $_[1] },
ES> '/' => sub { $_[0] / $_[1] } );
full circle. did you even see sam holden's post with the same solution?
the reason i posted was to stop the thread from going back to
symrefs. the code ref solution was shown and discussed already.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: 22 Aug 2003 16:24:22 -0700
From: marc.gibian@acm.org (Marc S. Gibian)
Subject: Perl build script woes doing Source Safe get
Message-Id: <8df11a0.0308221524.5f5fe3a5@posting.google.com>
I have a Perl script that I have been using to perform builds. This
script uses the source safe command line to fetch files into the
workspace before doing any building. It does very rigorous error
checking to be sure no problems go unnoticed during the build process.
The fetch portion of this script has worked well for a number of
months.
Yesterday I implemented a new feature. The original script fetched the
latest version of all files, performed the build, and then at the very
end attached a build label to the latest version of all files (hoping
there had been no divergence between the fetch and the label steps).
My change is to very early in the build label the latest version of
the files, and then fetch the labeled version of all files. This is
failing, reporting an error 25600, "No such file or directory".
I tested one last variation... I took the current script and removed
the label argument from the get command and this is now failing with
the same 25600 error.
The command line(s) I am using are:
ss get $/project -R -I-Y -V"MYBUILDLABEL"
ss get $/project -R -I-Y
Immediately prior to the get I do a ss Workfold to set the working
folder to the desired target location, and that is succeeding with no
problem. I have tried running the command line by hand in a shell
window and THAT works without error.
My questions:
1 - Why is source safe reporting a non-zero error code? What error is
it reporting?
2 - Is my script just being overly sensitive to warnings and such, or
is there something here I can fix so that the "get" begins returning
zero (again)?
Thanks very much for your help,
Marc
------------------------------
Date: 22 Aug 2003 18:12:11 -0700
From: altalingua@hotmail.com (David Morel)
Subject: Problem with split function
Message-Id: <60c4a7b1.0308221712.18fc7b18@posting.google.com>
Hi all,
I am having a problem with the split function.
Here is my code:
$_ = "123 a 456 b 789 c";
my @words = split /[^a-z]+/, $_;
print $words[0], $words[1], $words[2];
I want the output to be: abc
However, the actual output of this code is: ab
($words[0] is equal to "" not "a").
What am I doing wrong? Why isn't the output abc?
------------------------------
Date: Sat, 23 Aug 2003 12:46:02 +1000
From: Simon Taylor <simon@unisolve.com.au>
Subject: Re: Problem with split function
Message-Id: <bi6kkb$27vj$1@otis.netspace.net.au>
David Morel wrote:
> Hi all,
>
> I am having a problem with the split function.
> Here is my code:
>
> $_ = "123 a 456 b 789 c";
> my @words = split /[^a-z]+/, $_;
> print $words[0], $words[1], $words[2];
>
> I want the output to be: abc
> However, the actual output of this code is: ab
> ($words[0] is equal to "" not "a").
>
> What am I doing wrong? Why isn't the output abc?
It's my understanding that split() sees your first delimiter,
"123 " and is dutifully returning the first (empty) field that
is delimited by it. The zero-width one that is just there to the
left of "123 "!
You could resort to:
my (undef, @words) = split /[^a-z]+/, $_;
Or re-order your data source (assuming you have control over it), so
that the first delimiter appears *after* the first thing being delimited.
As "perldoc -f perlsplit" says:
"By default, empty leading fields are
preserved, and empty trailing ones are deleted."
Hope this helps.
Simon Taylor
------------------------------
Date: Fri, 22 Aug 2003 22:59:22 -0400
From: Buck <Nekid@jaybird.com>
Subject: Re: Problem with split function
Message-Id: <pan.2003.08.23.02.59.20.452321@jaybird.com>
On Fri, 22 Aug 2003 18:12:11 -0700, David Morel wrote:
> Hi all,
>
> I am having a problem with the split function.
> Here is my code:
>
> $_ = "123 a 456 b 789 c";
> my @words = split /[^a-z]+/, $_;
> print $words[0], $words[1], $words[2];
>
> I want the output to be: abc
> However, the actual output of this code is: ab
> ($words[0] is equal to "" not "a").
>
> What am I doing wrong? Why isn't the output abc?
You are using the letters as the common delimiter.
If you want the numbers to be the field separators:
my @words = split /\d+/, $_;
This will produce @words[0..3] :
" a b c"
$_="123 a 456 b 789 c";
print grep { /[a-z]/g } (split /\s+/,$_);
Results in: abc
Regards,
Rich
------------------------------
Date: Sat, 23 Aug 2003 00:33:38 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re: Pure Perl SQL server
Message-Id: <3F46B645.1050106@rochester.rr.com>
Peter Cooper wrote:
> Does anyone know of a pure Perl SQL server? I have noticed the rise of 'pure
> Perl' modules for things like XML parsing, and the pure Perl DBD::MySQLPP,
> but have never seen anything as ambition as a pure Perl SQL server.
>
> I am not entirely sure as to how useful such a thing would be, although it'd
> make a cute part time project, as there's bound to be tons of things I'd
> learn along the way. With Perl6/Parrot approaching rapidly, I believe such
> pure Perl systems could come into their own, as Perl's speed rockets up the
> y-axis.
...
> I have looked at SQL::Statement which does a little parsing for DBD::CSV,
> although I have yet to take a good look into DBD::CSV itself. I believe
> there's potential to developing a 'reasonably' powerful SQL engine in pure
> Perl, and if it's developed with Perl 6 in mind, it may become a rather
> useful tool in the future.
...
> Peter Cooper
Hmmmmm...well, if you use DBI::PurePerl in conjunction with DBD::CSV, it
looks like you probably get a pure Perl SQL database implementation.
There is also DBD::RAM, which also appears to be pure Perl. I'm not
sure just what you mean by "SQL server".
--
Bob Walton
------------------------------
Date: Sat, 23 Aug 2003 01:59:22 +0100
From: "Peter Cooper" <newsfeed@boog.co.uk>
Subject: Re: Pure Perl SQL server
Message-Id: <bi6ec2$5f9gv$2@ID-194358.news.uni-berlin.de>
Thanks for replying, Bob.
> Hmmmmm...well, if you use DBI::PurePerl in conjunction with DBD::CSV, it
> looks like you probably get a pure Perl SQL database implementation.
> There is also DBD::RAM, which also appears to be pure Perl. I'm not
> sure just what you mean by "SQL server".
Good points. I wanted someone to question my idea in this way, so I can at
least attempt to prove/disprove its validity in my head. I didn't know about
DBD::RAM before, but I've checked that out, and it seems interesting.. I'll
have to run a few 'experiments' with it :-)
By "SQL server", I mean replicating something like MySQL entirely in Perl.
So, yeah, you'd create a DBD, and use DBI, as you would with anything else,
but the actual database /backend/ (like your MySQL, Oracle, etc) would be
Perl code.. and it wouldn't be CSV, or in RAM.. but fast binary files.
The featureset would be comparable to an early MySQL, better than
SQL::Statement can parse (and therefore better than DBD::CSV or DBD::RAM can
handle), and using binary files. It'd be no speed champion, but when Perl 6
is out and about, it could be 'reasonably' fast, thanks to Parrot, and it'd
be entirely interpreted. For people who can't even create sockets (for
security purposes), you could also make it run in a 'command line' form.
Just pipedreams, I guess, but I'll be sure to look into it further. Any
further queries or comments would be most appreciated though.
Pete
------------------------------
Date: Sat, 23 Aug 2003 01:08:24 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re: stemming algotithms in perl
Message-Id: <3F46BE69.50703@rochester.rr.com>
monkeys paw wrote:
> Is there an established code base for stemming in perl.
>
> For instance, if i want to match phrases in a string,
> my base phrase would be "race", but i would also want
> to automatically match "races", and "racing", "raced", etc...
>
> I thought there may be a module or ?? out there...
>
Did you miss Lingua::Stem when you visited CPAN?
--
Bob Walton
------------------------------
Date: Sat, 23 Aug 2003 03:09:44 -0000
From: "David K. Wall" <usenet@dwall.fastmail.fm>
Subject: Re: Text::Autoformat and 'psychosis'
Message-Id: <Xns93DFEB9E5919Fdkwwashere@216.168.3.30>
I wrote:
> Here's some weirdness. When I run
>
> use Text::Autoformat;
> print autoformat 'PSYCHOSIS', {case=>'lower'};
>
> the output is 'PSychosis' instead of 'psychosis'. Other variations
> give assorted weirdnesses. (See code below)
[snip]
Followup: I emailed Damian Conway and it turns out he fixed that bug in May
2003 in version 1.12. I had version 1.10, something I forgot to mention.
--
David Wall
------------------------------
Date: Fri, 22 Aug 2003 15:24:26 -0700
From: "Islaw" <islaw@adexec.com>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <bi6531$5n7sd$1@ID-196529.news.uni-berlin.de>
Trent Curry wrote:
> I know this group (comp.lang.perl, not comp.lang.perl.misc) has been
> dead for a long time now, albeit my news server has always carried
> it, but seemingly locally to the server since it is always empty but
> I can still post to it.
>
> I also noticed that groups.google .com carries comp.lang.perl as well
> as comp.lang.perl.misc, so there seems to be the existence of this
> group still, yes?
>
> From what I heard a while back, comp.lang.perl simply changed it's
> name to comp.lang.perl.misc.
>
> What was the reason for this? Does anyone know?
Like others had said, they wanted to basically match the naming convention
that the "big 8" groups used.
> I have newer understood why the name would be changed instead of just
> having two groups. It probably would of lessened the amount of trouble
> comp.lang.perl.misc has had in the past years, many of which seemed
> to lead to the group name which was very misleading (as most groups
> with "misc" in the name suggestion "miscellaneous", yet many regulars
> would always point out that it wasn't, though I never actually saw an
> explanation of what "misc" was suppose to stand for in this case.)
>
> So I ask, what is the story here? The original control messages only
> say that this group has taken over the original. But WHY was this
> name change even done in the first place?
Personally I think they should have left it. There are so many groups out
ther havign to do with a certain language, like
comp.lang.c++
comp.lang.c
comp.lang.java
comp.lang.javascript
Some of thosel ike comp.lang.c++ and comp.lang.java have the original group
and a few child groups.
Furthur more, so many times in the past there have been people trying to
push the idea that ".misc" in "comp.lang.perl.misc" dcoesnt stand for
miscellaneous and instead just a very limited discussion of the language. I
agree 100% that ".misc" has been a source of a lot of trouble. For petes
sake, if you are goign to rename a group to include the word or phrase
"misc" in it (espically in a group where popularity was growing at ahealthy
rate) you are going to have a lot people coming there because the name would
lead one to beleive you could ask questions even loosely pertaining to Perl
with any fear of flaming or what not.
Thats my 2cents, canadian
--
Islaw
------------------------------
Date: Sat, 23 Aug 2003 01:13:16 +0200
From: "Alan J. Flavell" <flavell@mail.cern.ch>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <Pine.LNX.4.53.0308230053430.19116@lxplus065.cern.ch>
On Fri, Aug 22, Matt Garrish inscribed on the eternal scroll:
> I'm not interested in eliciting a hudson-esque reponse, but the inference of
> .misc does seem at odds with the willingness of some people to discuss
> anything beyond specific code examples
As should be clear from Jon Bell's reply: what *.foo.misc is supposed
to mean on a big-8 group is "anything that would have been on-topic
for *.foo, minus those topics which have their own specific group".
It does *not* mean "anything which is remotely related to foo, no
matter that there might be several other groups where the issue would
be more on-topic".
Of course, as in any social situation there are occasions for
off-topic levity, but I don't try that on groups where I'm not a
reasonably regular participant and have a rough measure of the group's
dynamics, as it can so easily blow up in one's face.
> It isn't much of a stretch for me to understand why new programmers trying
> to get their scripts to run in Apache (simply as an example that occurs
> quite frequently), would think it perfectly reasonable to post to
> comp.lang.perl.misc to ask other Perl programmers what the problem might be
> (without expecting to be flamed).
My impression is that other regulars have seen enough times before
where off-topic questions have got misleading answers, and would wish
to save the questioner from that by nudging them in the direction of a
more-appropriate group. Of course, sometimes the questioner has no
clear idea just where their problem lies, and for sure a degree of
tolerance is then appropriate, but it has to be understood that on a
technical discussion group, technical details are the order of the
day, and warm fuzzies are for a different venue. Anyhow: if the group
advises them that their problem seems to be more in the nature of an
Apache configuration problem than a Perl programming problem, the
questioner would be well advised to take the answer with good grace.
> One would assume that Perl programmers
> would probably be familiar with setting up the environment in which to run
> their scripts,
That's where you'd be dead wrong, for many of the serious users of
Perl here. (Myself, for one, excluded... but then, maybe I'm not
serious enough... ;-)
> and be willing to help.
I never cease to be amazed at the patience and willingness to help
shown by many of the regulars here in the face of advanced stupidity,
where I simply drop the questioner quietly into the killfile and go
about my business. But there are not a few occasions when that "help"
may very properly consist of a reference to a more appropriate group
or forum.
> My question is: has anyone considered a c.l.learn.perl group?
Has anyone considered reading the not-insignificant previous
discussions on that topic area? :-}
------------------------------
Date: Fri, 22 Aug 2003 17:19:11 -0700
From: "Trent Curry" <tcurrey@no.no.no.i.said.no>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <bi6bu4$jes$1@news.astound.net>
Alan J. Flavell wrote:
> On Fri, Aug 22, Matt Garrish inscribed on the eternal scroll:
>
>> I'm not interested in eliciting a hudson-esque reponse, but the
>> inference of .misc does seem at odds with the willingness of some
>> people to discuss anything beyond specific code examples
>
> As should be clear from Jon Bell's reply: what *.foo.misc is supposed
> to mean on a big-8 group is "anything that would have been on-topic
> for *.foo, minus those topics which have their own specific group".
Yes, but there are many group hierarchys whrre there is a base group, say
comp.blah, comp.blah.something, comp.blah.misc. The fact the on many news
servers BOTH comp.lang.perl and comp.lang.perl.misc exist didn't help the
fact that .misc would be seen by many as miscellaneous. Many over groups
that started with base groups also fell victum to this, though this group is
probably one of the worst cases I've seen.
> It does *not* mean "anything which is remotely related to foo, no
> matter that there might be several other groups where the issue would
> be more on-topic".
Yes, but this is not the definition that most would come to from the name
".misc".
> Of course, as in any social situation there are occasions for
> off-topic levity, but I don't try that on groups where I'm not a
> reasonably regular participant and have a rough measure of the group's
> dynamics, as it can so easily blow up in one's face.
>
>> It isn't much of a stretch for me to understand why new programmers
>> trying to get their scripts to run in Apache (simply as an example
>> that occurs quite frequently), would think it perfectly reasonable
>> to post to comp.lang.perl.misc to ask other Perl programmers what
>> the problem might be (without expecting to be flamed).
>
> My impression is that other regulars have seen enough times before
> where off-topic questions have got misleading answers, and would wish
> to save the questioner from that by nudging them in the direction of a
> more-appropriate group. Of course, sometimes the questioner has no
> clear idea just where their problem lies, and for sure a degree of
> tolerance is then appropriate, but it has to be understood that on a
> technical discussion group, technical details are the order of the
> day, and warm fuzzies are for a different venue. Anyhow: if the group
> advises them that their problem seems to be more in the nature of an
> Apache configuration problem than a Perl programming problem, the
> questioner would be well advised to take the answer with good grace.
But can't you understand that (at least part of) the REASON that people were
asking some of those so-called off topic and cgi related questions IS the
name of the group.
>> One would assume that Perl programmers
>> would probably be familiar with setting up the environment in which
>> to run their scripts,
>
> That's where you'd be dead wrong, for many of the serious users of
> Perl here. (Myself, for one, excluded... but then, maybe I'm not
> serious enough... ;-)
How so? Just becuase you and some of your collegues don't use Perl via web
servers, that it isn't something many people use? One could say that one of
the biggest usages of Perl next to shell based/utility scripting is via
Apache www servers (as well as nearly anyother www server available today.)
Maybe this is one of the reasons that the idea of having a *.perl.cgi has
been proposed over and over. Hell, there ARE perl.cgi groups in foriegn
languages, but not the english big 8.
I even once saw someoen post an idea for a perl.apache_cgi, which may not of
been so bad, considering virtually EVERY unix based distro comes with Apache
and Perl. Just a thought...
Please face the reality, Perl IS widely used on web servers, just as it is
extreamly widely used in the shell.
>> and be willing to help.
>
> I never cease to be amazed at the patience and willingness to help
> shown by many of the regulars here in the face of advanced stupidity,
> where I simply drop the questioner quietly into the killfile and go
> about my business. But there are not a few occasions when that "help"
> may very properly consist of a reference to a more appropriate group
> or forum.
>
>> My question is: has anyone considered a c.l.learn.perl group?
>
> Has anyone considered reading the not-insignificant previous
> discussions on that topic area? :-}
Exactly what is wrong wiht a group like that? If you ask me the constant
attitude towards that matter in this group as long been part of the problem.
"Not everyone is born a genius." - some poster
------------------------------
Date: Sat, 23 Aug 2003 00:30:39 GMT
From: "Luriel" <luriel@gfy.yahoo.com>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <PAy1b.4299$iW6.682@newssvr27.news.prodigy.com>
Alan J. Flavell wrote:
> On Fri, Aug 22, Matt Garrish inscribed on the eternal scroll:
[....]
>> It isn't much of a stretch for me to understand why new programmers
>> trying to get their scripts to run in Apache (simply as an example
>> that occurs quite frequently), would think it perfectly reasonable
>> to post to comp.lang.perl.misc to ask other Perl programmers what
>> the problem might be (without expecting to be flamed). One would
>> assume that Perl programmers would probably be familiar with
>> setting up the environment in which to run their scripts, and be
>> willing to help.
>
> That's where you'd be dead wrong, for many of the serious users of
> Perl here. (Myself, for one, excluded... but then, maybe I'm not
> serious enough... ;-)
And you can speak for each_and_every person in this group? Do you really
think no "serious" programmer would use it on a www platform??? Is it really
any wonder why so many have come in here about using Perl as cgi on Apache,
since it comes preinstalled on most unix/linux bases systems, which also
come bundled with Perl? I'd frankly be amazed if most "serious [Perl] users"
have not found web bases usages for this powerful language. Just because you
may not find uses with www application doesn't mean others don't and I don't
think you have any right to speak for others like this.
No offense instended Flavell, but I think on this note is "where you'd be
dead wrong".
--
Luriel
------------------------------
Date: Sat, 23 Aug 2003 02:53:12 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <bi6e50$5dali$1@ID-184292.news.uni-berlin.de>
Luriel wrote:
> No offense instended Flavell, but I think on this note is "where
> you'd be dead wrong".
Hey, relax, Luriel! There was some irony in Alan's post which I
thought was obvious. Seems as if it wasn't that obvious, after all. ;-)
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 22 Aug 2003 21:06:13 -0400
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <m6z1b.4122$PJ2.350266@news20.bellglobal.com>
"Alan J. Flavell" <flavell@mail.cern.ch> wrote in message
news:Pine.LNX.4.53.0308230053430.19116@lxplus065.cern.ch...
>
> As should be clear from Jon Bell's reply: what *.foo.misc is supposed
> to mean on a big-8 group is "anything that would have been on-topic
> for *.foo, minus those topics which have their own specific group".
>
> It does *not* mean "anything which is remotely related to foo, no
> matter that there might be several other groups where the issue would
> be more on-topic".
>
My intention is not to change clp.misc to anything it isn't already, nor am
I trying to advocate that. I'm simply positing the idea that maybe a
clp.learn would be a useful addition to the hierarchy, as it would fill a
different need.
>
> My impression is that other regulars have seen enough times before
> where off-topic questions have got misleading answers, and would wish
> to save the questioner from that by nudging them in the direction of a
> more-appropriate group. Of course, sometimes the questioner has no
> clear idea just where their problem lies, and for sure a degree of
> tolerance is then appropriate, but it has to be understood that on a
> technical discussion group, technical details are the order of the
> day, and warm fuzzies are for a different venue.
Which furthers my point. Diversity is a good thing, and warm and fuzzy group
for beginners would likely: a) keep the discussions in .misc more
technical-based; and b) provide a more obvious and beginner-friendly
discussion group for the newbies of the world.
You also can't expect someone to be gracious to you when you're
condescending and rude to them (and I don't mean you personally). I've been
reading this group on-and-off for about 3 or 4 years now, and there are some
people who, no matter how many times and how many different people criticize
their lacking manners, seem to believe they have no faults. CLPM is a great
forum for the novice to advanced programmer, but is more often a black hole
for the beginner to novice.
>
> Has anyone considered reading the not-insignificant previous
> discussions on that topic area? :-}
>
They also tend to go nowhere, as they inevitably fall into bickering about
whether clpm is the be-all and end-all of perl groups (which is also why I
put in the concluding comment... : )
I suppose I could have phrased it differently for those who have seen the
question before: is it perhaps time to do something?
Matt
------------------------------
Date: Sat, 23 Aug 2003 03:16:36 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <o0B1b.2509$vy5.2219@nwrddc01.gnilink.net>
Matt Garrish wrote:
> "Rafael Garcia-Suarez" <rgarciasuarez@free.fr> wrote in message
> news:slrnbkcsrc.gn1.rgarciasuarez@dat.local...
> It isn't much of a stretch for me to understand why new programmers
> trying to get their scripts to run in Apache (simply as an example
> that occurs quite frequently), would think it perfectly reasonable to
> post to comp.lang.perl.misc to ask other Perl programmers what the
> problem might be (without expecting to be flamed).
Except that Apache and Perl have pretty much nothing to do with each other?
> One would assume
> that Perl programmers would probably be familiar with setting up the
> environment in which to run their scripts, and be willing to help.
Certainly. Just set your path to perl (or perl.exe on Windows) and off you
go.
What does that have to do with Apache? I'm writing Perl programs on and off
for the last 10 years or so. I've never used Apache or any other web server
for that matter.
jue
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
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 5412
***************************************
