[17954] in Perl-Users-Digest
Perl-Users Digest, Issue: 114 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Jan 22 00:10:31 2001
Date: Sun, 21 Jan 2001 21:10:13 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <980140213-v10-i114@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Sun, 21 Jan 2001 Volume: 10 Number: 114
Today's topics:
Re: Posting Guidelines (was Re: Perl - Bytecode, Compil <gracenews@optusnet.com.au>
Re: Posting Guidelines (was Re: Perl - Bytecode, Compil <wyzelli@yahoo.com>
Re: Posting Guidelines (was Re: Perl - Bytecode, Compil (Tad McClellan)
Printing problems <tvesty@cseast.com>
Re: Printing problems <sdmeisner@SPAMGUARDyahoo.com>
Re: Printing problems <bwalton@rochester.rr.com>
Re: Printing problems (Martien Verbruggen)
Quick Newbie Qeustion please... <ofirb@jdc.org.il>
RFD: misc.jobs.fields.programming.perl <brannon@lnc.usc.edu>
Specifying mySQL output columns from HTML form checkbox swan_daniel@my-deja.com
Re: uploading files dtbaker_dejanews@my-deja.com
Re: uploading files dtbaker_dejanews@my-deja.com
warning! moronzilla is back <uri@sysarch.com>
Re: warning! moronzilla is back <callgirl@la.znet.com>
Re: warning! moronzilla is back <uri@sysarch.com>
Re: Words in Perl - Pulling Hair <uri@sysarch.com>
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 22 Jan 2001 12:48:00 +1000
From: "Jeffrey Grace" <gracenews@optusnet.com.au>
Subject: Re: Posting Guidelines (was Re: Perl - Bytecode, Compile to C, Perl2EXE)
Message-Id: <3a6b9f6b$0$15473$7f31c96c@news01.syd.optusnet.com.au>
"Tad McClellan" <tadmc@augustmail.com> wrote in message
news:slrn96lnto.gb2.tadmc@tadmc26.august.net...
>
> Not now and not it this thread.
>
> When it is autoposted you can make a suggestion here in a thread
> rooted at the autopost :-)
Ok.
> [ but when discussion _does_ open keep in mind that we must be
> ruthless in maintaining a relatively small size. We don't have
> much wiggle room. To add new stuff, it would need to be More
> Important than some existing point, so we can delete a point
> to make room for the new one.
> ]
Thought this may have been the case.
>
> Pointing them to a place "out on the web" that has the exact same
> info as is already on their own hard disk seems roundabout.
>
> I should probably add "perldoc perldoc" in there somewhere though.
> Please mention that again when the autopost starts showing up.
>
If I see it and remember I will.
>
> >Also in the before posting section, maybe you could remind them about
common
> >lines that they should use,
>
>
> Did you see the "Do not expect people to do a machine's work" section?
>
>
> >such as:
> >#! /bin/usr/perl -Tw
> >use Strict;
> ^
>
> We wouldn't want to include code with syntax errors though :-)
Thats a syntax error?? I cut and pasted it (just checked it then to be sure)
from a working, error free CGI script. Can't remember exactly where I got
that line from originally, but I believe it was cut and pasted from a post
on this newsgroup.
>
> Tainting is not universally applicable (eg. programs that don't take
> external input), so that shouldn't be in there.
>
But it doesn't hurt (IAFAIK), and its a good habit isn't it?
> No, I will resist to the end adding anything specific to an
> application area that Perl might be used in. Perl is used in
> lots and lots of places, which ones deserve coverage and which
> ones don't?
no worries.
>
> If we don't do application-specific stuff, then we don't need
> to wrestle with the answer to that question. Laziness in action!
>
;-)
> Checking the Perl FAQ would cut down on the number of posts too,
> it just does not happen as it should :-(
People stretched for time simply don't have the luxury of going through the
rather volumous FAQ for fun.
> Tad McClellan SGML consulting
> tadmc@augustmail.com Perl programming
> Fort Worth, Texas
------------------------------
Date: Mon, 22 Jan 2001 12:42:35 +0930
From: "Wyzelli" <wyzelli@yahoo.com>
Subject: Re: Posting Guidelines (was Re: Perl - Bytecode, Compile to C, Perl2EXE)
Message-Id: <7qNa6.8$zO4.3917@vic.nntp.telstra.net>
> >
> > >such as:
> > >#! /bin/usr/perl -Tw
> > >use Strict;
> > ^
> >
> > We wouldn't want to include code with syntax errors though :-)
>
> Thats a syntax error?? I cut and pasted it (just checked it then to be
sure)
> from a working, error free CGI script. Can't remember exactly where I
got
> that line from originally, but I believe it was cut and pasted from a
post
> on this newsgroup.
>
use strict;
(lowercase 's')
Maybe if the use strict is corrected in the CGI script, it will start
having errors.... :-) (that were missed previously)
Wyzelli
--
push@x,$_ for(a..z);push@x,' ';
@z='092018192600131419070417261504171126070002100417'=~/(..)/g;
foreach $y(@z){$_.=$x[$y]}y/jp/JP/;print;
------------------------------
Date: Mon, 22 Jan 2001 04:39:43 GMT
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Posting Guidelines (was Re: Perl - Bytecode, Compile to C, Perl2EXE)
Message-Id: <slrn96n74b.hsa.tadmc@tadmc26.august.net>
Jeffrey Grace <gracenews@optusnet.com.au> wrote:
>"Tad McClellan" <tadmc@augustmail.com> wrote in message
>news:slrn96lnto.gb2.tadmc@tadmc26.august.net...
>> >such as:
>> >#! /bin/usr/perl -Tw
>> >use Strict;
>> ^
>>
>> We wouldn't want to include code with syntax errors though :-)
>
>Thats a syntax error??
Yes.
There _is_ a strict.pm pragma.
I cannot find a mention of any Strict.pm module at search.cpan.org.
>I cut and pasted it (just checked it then to be sure)
>from a working, error free CGI script.
You must have a local Strict.pm module then (or a case-insensitive
filesystem).
>Can't remember exactly where I got
>that line from originally, but I believe it was cut and pasted from a post
>on this newsgroup.
^^^^^^^^^^^^^^^^^
No guarantee, that.
It kinda matters who it was who said it.
>> Tainting is not universally applicable (eg. programs that don't take
>> external input), so that shouldn't be in there.
>>
>But it doesn't hurt (IAFAIK), and its a good habit isn't it?
It is an irreplaceable habit for CGI programmers, but not
necessarily for Perl programmers.
>> Checking the Perl FAQ would cut down on the number of posts too,
>> it just does not happen as it should :-(
>
>People stretched for time
are looking to have hundreds/thousands of *other people* look
it up for them?
You can't be serious.
If you do not have time to check the FAQ, then you cannot post.
There is no exception for the Really Important People that are
in too much of a hurry to check first.
And on top of that, finding the answer on their own hard disk will
SAVE the time of the time-starved folks while simultaneously
avoiding wasting the time of hundreds of their peers.
A win-win situation.
>simply don't have the luxury of going through the
If you aim to post to the Perl newsgroup, then checking the FAQ
is NOT a "luxury". It is a "requirement" here, as in most Big 8
newsgroups.
>rather volumous FAQ for fun.
I didn't say _read_ the FAQ. I said _check_ the FAQ.
I specifically avoid saying "read" the FAQ to avoid that very
misconception.
It is not expected that you read the Perl FAQ before posting.
It is expected that you check the Perl FAQ before posting.
(and then read applicable parts, of course)
Word searching shouldn't depend much on the FAQ's size,
unless we're counting milliseconds :-)
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sun, 21 Jan 2001 23:52:04 GMT
From: <tvesty@cseast.com>
Subject: Printing problems
Message-Id: <ECKa6.5792$Jw.1095652@typhoon2.ba-dsg.net>
Hi all,
I'm trying to print a large report from a data file, but the program stops
working after 300 lines or so. I could fid no problem so I mad a simple
script to test print. It's a simple loop. It also stops printing around
300 lines or so. I can print more lines if I shorten the length of each
line, but still not enough.
Is this a shortcoming inherent to perl or am I doing something wrong. Here
is the short test script. Thanks!!
#!/usr/bin/perl
print "Content-type: text/html\n\n";
@line='';
for ($i= 1; $i<3000; $i +=1){
$line[$i]="$i and blah blah blah blah blah blah blah blah blah blah
blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
blah blah blah blah blah blah blah";
print "$line \n";
}
------------------------------
Date: Mon, 22 Jan 2001 02:18:12 GMT
From: "Sean Meisner" <sdmeisner@SPAMGUARDyahoo.com>
Subject: Re: Printing problems
Message-Id: <ELMa6.147$H27.55456@sapphire.mtt.net>
This code contains an error that will cause it to print
nothing but a bunch of blank lines anyway.. please
test the test script and repost a copy that produces
the error you describe..
<tvesty@cseast.com> wrote in message
news:ECKa6.5792$Jw.1095652@typhoon2.ba-dsg.net...
> Hi all,
>
> I'm trying to print a large report from a data file, but the program stops
> working after 300 lines or so. I could fid no problem so I mad a simple
> script to test print. It's a simple loop. It also stops printing around
> 300 lines or so. I can print more lines if I shorten the length of each
> line, but still not enough.
>
> Is this a shortcoming inherent to perl or am I doing something wrong.
Here
> is the short test script. Thanks!!
>
>
> #!/usr/bin/perl
>
> print "Content-type: text/html\n\n";
> @line='';
>
>
> for ($i= 1; $i<3000; $i +=1){
> $line[$i]="$i and blah blah blah blah blah blah blah blah blah
blah
> blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
> blah blah blah blah blah blah blah";
> print "$line \n";
> }
>
>
>
>
>
>
------------------------------
Date: Mon, 22 Jan 2001 02:18:22 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re: Printing problems
Message-Id: <3A6B9938.C02FFF65@rochester.rr.com>
tvesty@cseast.com wrote:
...
> I'm trying to print a large report from a data file, but the program stops
> working after 300 lines or so. I could fid no problem so I mad a simple
> script to test print. It's a simple loop. It also stops printing around
> 300 lines or so. I can print more lines if I shorten the length of each
> line, but still not enough.
>
> Is this a shortcoming inherent to perl or am I doing something wrong. Here
> is the short test script. Thanks!!
>
> #!/usr/bin/perl
>
> print "Content-type: text/html\n\n";
> @line='';
>
> for ($i= 1; $i<3000; $i +=1){
> $line[$i]="$i and blah blah blah blah blah blah blah blah blah blah
> blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
> blah blah blah blah blah blah blah";
> print "$line \n";
> }
Well, by "print", I assume you mean "display on a web browser"? Your
script looks like it is intended to be run as a CGI program. If so, it
won't, as given, display anything. That is because you assign values to
elements of array @line, and then print scalar $line, which has not been
assigned a value. The output then consists of 2999 lines of a space
character followed by a newline. Since it is HTML, that is an HTML page
that consists of only whitespace, all of which will be ignored.
In the event that the above isn't really the program you ran, and that
the print statement actually reads:
print "$line[$i] \n";
then the problem probably doesn't reside in Perl, but more likely in
your web server or browser -- is there a limit specified on output
size? You say your program "stops working" after 300 lines. What do
you mean by that? Does it generate an error message? If so, what does
it say? What is in your server log files? There is also the
possibility (probably unlikely since you really don't have all that many
lines) that you are running into a memory limitation, since you are
storing lots of lines in array @line. Maybe your web server or its
operating system has a memory limit for CGI processes?
Also, you neglected to specify the -w switch and to use strict;. Either
or both of those would give you handy pointers to problems, including
the problem I pointed out above. And if it is indeed a CGI script, you
are really missing the boat by not using the CGI module.
HTH.
--
Bob Walton
------------------------------
Date: Mon, 22 Jan 2001 02:29:14 GMT
From: mgjv@tradingpost.com.au (Martien Verbruggen)
Subject: Re: Printing problems
Message-Id: <slrn96n6lt.213.mgjv@verbruggen.comdyn.com.au>
On Sun, 21 Jan 2001 23:52:04 GMT,
tvesty@cseast.com <tvesty@cseast.com> wrote:
> Hi all,
>
> I'm trying to print a large report from a data file, but the program stops
> working after 300 lines or so. I could fid no problem so I mad a simple
> script to test print. It's a simple loop. It also stops printing around
> 300 lines or so. I can print more lines if I shorten the length of each
> line, but still not enough.
>
> Is this a shortcoming inherent to perl or am I doing something wrong. Here
> is the short test script. Thanks!!
>
>
> #!/usr/bin/perl
no -w, and no use strict. you are NOT helping yourself finding the
problem. If you enable both, it'll point out that there's something
wrong with your test script.
Besides that, please read the Perl FAQ, section 9 before posting
again. Make sure that you follow the advice in there about debugging
CGI programs.
> print "Content-type: text/html\n\n";
> @line='';
Why are you assigning a scalar to a list? If you want an empty list,
use:
@line = ();
Since you're not using strict, you don't even need to do this. arrays,
by default, are empty when they first get used.
And, if you use strict, which you should, all you have to do is:
my @line;
> for ($i= 1; $i<3000; $i +=1){
for (my $i = 0; $i < 3000; $i++)
{
> $line[$i]="$i and blah blah blah blah blah blah blah blah blah blah
> blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
> blah blah blah blah blah blah blah";
> print "$line \n";
> }
$line and @line have nothing to do with each other. Something you
would have known, if you only had asked Perl to tell you.
nd why do you assign the line to an array, and then print the array
element out? Why not just print it directly?
After fixing the problems that -w point out, the program runs fine.
There are no problems with Perl printing more than 300 lines, or
having more than 300 lines in an array, as long as your machine has
the memory for it. If it doesn't, you need to get more. Perl will tell
you when it runs out of memory.
Martien
--
Martien Verbruggen |
Interactive Media Division | If it isn't broken, it doesn't have
Commercial Dynamics Pty. Ltd. | enough features yet.
NSW, Australia |
------------------------------
Date: Sun, 21 Jan 2001 09:00:27 +0200
From: "Ofir" <ofirb@jdc.org.il>
Subject: Quick Newbie Qeustion please...
Message-Id: <94e1di$6h$1@news.netvision.net.il>
Hi all,
I want to be able to determine how many lines are in a file.
What is the way (subroutine) to check the total number of lines written in a
file?
TIA,
Ofir
------------------------------
Date: Mon, 22 Jan 2001 01:16:40 GMT
From: Terrence Brannon <brannon@lnc.usc.edu>
Subject: RFD: misc.jobs.fields.programming.perl
Message-Id: <980126200.16909@isc.org>
REQUEST FOR DISCUSSION (RFD)
unmoderated group misc.jobs.fields.programming.perl
This is a formal Request For Discussion (RFD) for the creation of a
world-wide unmoderated Usenet newsgroup misc.jobs.fields.programming.perl.
This is not a Call for Votes (CFV); you cannot vote at this time.
Procedural details are below.
Newsgroup line:
misc.jobs.fields.programming.perl Perl job announcements.
RATIONALE: misc.jobs.fields.programming.perl
misc.jobs.fields.programming.perl will create a Usenet forum for the
announcement of jobs related to the Perl programming language.
CHARTER: misc.jobs.fields.programming.perl
misc.jobs.fields.programming.perl is for the sharing of job announcements
concerning the Perl programming language.
END CHARTER.
PROCEDURE:
This is a request for discussion, not a call for votes. In this phase
of the process, any potential problems with the proposed newsgroups
should be raised and resolved. The discussion period will continue
for a minimum of 21 days (starting when the first RFD for this
proposal is posted to news.announce.newsgroups), after which a Call
For Votes (CFV) may be posted by a neutral vote taker if the
discussion warrants it. Please do not attempt to vote until this
happens.
All discussion of the proposal should be posted to news.groups.
This RFD attempts to comply fully with the Usenet newsgroup creation
guidelines outlined in "How to Create a New Usenet Newsgroup" and "How
to Format and Submit a New Group Proposal". Please refer to these
documents (available in news.announce.newgroups) if you have any
questions about the process.
DISTRIBUTION:
news.announce.newgroups
news.groups
comp.lang.perl.misc
alt.perl
Proponent: Terrence Brannon <brannon@lnc.usc.edu>
------------------------------
Date: Sun, 21 Jan 2001 23:48:08 GMT
From: swan_daniel@my-deja.com
Subject: Specifying mySQL output columns from HTML form checkboxes?
Message-Id: <YyKa6.48055$FH5.3732071@news0.telusplanet.net>
I wish to be able to specify which columns of a SQL query to output via
HTML checkboxes which will be processed by a perl CGI.
There are several difficulties in doing this, and I havn't found a perfect
solution to date. Can anyone point me towards to code samples of solutions
to this problem?
Thx in advance,
Dan.
--
............................................................................
"People ask me if we are going to stop applying [financial] pressure on the
Germans. I'll tell you now we will keep going back to the Germans again and
again... We expect this ammount may dwarf payments up to now"
-World Jewish Congress leader Edgar Bronfman
............................................................................
www.geocities.com/pentagon/bunker/1022 swan_daniel@my-dejanews.com
------------------------------
Date: Sun, 21 Jan 2001 23:43:30 GMT
From: dtbaker_dejanews@my-deja.com
Subject: Re: uploading files
Message-Id: <94fs71$a3k$1@nnrp1.deja.com>
In article <94fodi$3ck$1@newsx.cc.uic.edu>,
"Enrico Ng" <ng@fnmail.com> wrote:
> I know how to write files using open, print, close
> and how to upload files <form type=file
> but how to I write the perl code to get the file
-------
also, there are pretty good docs in the CGI module.
D
Sent via Deja.com
http://www.deja.com/
------------------------------
Date: Sun, 21 Jan 2001 23:41:22 GMT
From: dtbaker_dejanews@my-deja.com
Subject: Re: uploading files
Message-Id: <94fs31$9r9$1@nnrp1.deja.com>
In article <94fodi$3ck$1@newsx.cc.uic.edu>,
"Enrico Ng" <ng@fnmail.com> wrote:
> I know how to write files using open, print, close
> and how to upload files <form type=file
> but how to I write the perl code to get the file
----------
try using deja.com to search this group for the word "upload"
D
Sent via Deja.com
http://www.deja.com/
------------------------------
Date: Sun, 21 Jan 2001 23:48:09 GMT
From: Uri Guttman <uri@sysarch.com>
Subject: warning! moronzilla is back
Message-Id: <x7zogkwjpi.fsf@home.sysarch.com>
this should be a regularly posted notice.
our troll of the last year, moronzilla is back here. as always, she
preys on newbies who don't know better. look for any thread that is not
started by a newbie and you won't find her. she has no concept of
separating perl from the web, thinks using modules are not programming
(and how are modules created?), doesn't ever respond to corrections, and
in general is a flaming idiot.
so to all those who are seeing her for the first time, ignore her and
she will disappear like a bad dream. if you see followups to her,
politely email those respondents and tell them to stop. she has no power
if she is not listened too. sounds just like some stupid ghost story but
she is real enough and dangerous with her incorrect answers and perl4
attitudes. if you need any more proof just search dejanews for her posts
and you will see the futility of interacting with her.
this is a public warning to all in this group.
uri
--
Uri Guttman --------- uri@sysarch.com ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
------------------------------
Date: Sun, 21 Jan 2001 16:16:04 -0800
From: Kira <callgirl@la.znet.com>
Subject: Re: warning! moronzilla is back
Message-Id: <3A6B7BC4.890605E2@la.znet.com>
Uri Guttman wrote:
> this should be a regularly posted notice.
> our troll of the last year, moronzilla is back here. as always, she
> preys on newbies who don't know better. look for any thread that is not
> started by a newbie and you won't find her. she has no concept of
> separating perl from the web, thinks using modules are not programming
> (and how are modules created?), doesn't ever respond to corrections, and
> in general is a flaming idiot.
> so to all those who are seeing her for the first time, ignore her and
> she will disappear like a bad dream. if you see followups to her,
> politely email those respondents and tell them to stop. she has no power
> if she is not listened too. sounds just like some stupid ghost story but
> she is real enough and dangerous with her incorrect answers and perl4
> attitudes. if you need any more proof just search dejanews for her posts
> and you will see the futility of interacting with her.
> this is a public warning to all in this group.
I shall make a point to reproduce and post this
warning on a regular basis.
Entertaining post, Mr. Guttman. However not quite
as interesting as this five-hundred dollar bounty
on my head plastered all over the net. True story.
Another one of my fans, an affectionate fan such
as yourself, posted a five-hundred dollar wanted
poster via myriad public chats, wishing to learn
my true identity and whereabouts. If I remember
rightly, this wanted poster hit the net back in
1997. Best I know, nobody has ever collected this
reward. You should give it a shot; it would be just
compensation for your zealous protection of our
Perl Perl Land against this exceptionally dangerous
person, moi.
Godzilla!
------------------------------
Date: Mon, 22 Jan 2001 04:53:30 GMT
From: Uri Guttman <uri@sysarch.com>
Subject: Re: warning! moronzilla is back
Message-Id: <x7wvbow5kl.fsf@home.sysarch.com>
>>>>> "K" == Kira <callgirl@la.znet.com> writes:
K> I shall make a point to reproduce and post this
K> warning on a regular basis.
good. you should be protected from yourself as well.
K> Another one of my fans, an affectionate fan such as yourself,
K> posted a five-hundred dollar wanted poster via myriad public chats,
K> wishing to learn my true identity and whereabouts. If I remember
K> rightly, this wanted poster hit the net back in 1997. Best I know,
K> nobody has ever collected this reward. You should give it a shot;
K> it would be just compensation for your zealous protection of our
K> Perl Perl Land against this exceptionally dangerous person, moi.
i wouldn't spend a dime on tracking you down. usenet is free and so it
should stay. but it should not be sullied by those who would have it
revolve around their demented sense of perl skills. since you have no
one here who thinks you know anything about perl or programming, you
have no reason to be here. start your own cult of personality where you
can but not on this turf. the perl community has no interest in you and
you obviously have no interest in us. so leave and may you walk in
peace, just don't tread where we congregate. you would never show your
face at a perl monger's meeting, a perl conference, on #perl, on perl
web sites, etc. so why do you diecide to infest c.l.p.misc? is it
because you can prey on innocent newbies more easily here? on #perl you
would be banned, at any in person events you would be laughed at, any
journal would file your stuff in /dev/null. here is the only place where
you can even show your hidden self and not be filtered out
completely. so your tactics are well known your intentions are as
well. you have tried to disrupt this group with all sorts of false cries
of persecution, crimes and other unproven accusations. but of course you
never defend your perl statements with any logic which is the lingua
franca of computer geeks everywhere. let's see you enter some of the
more in depth threads. write some code that won't make anyone but a
total green perl newbie retch violently. discuss something without you
getting personal. i triple dog dare you to actually discuss code only
and keep focsued on that. but you won't. it is too scary for you to
expose yourself to the spotlight. you would rather stroke your psychoses
by cuddling up to newbies and trolling them into your spider's parlor.
so just do yourself and us a big favor and go back on vacation from
here. it was awful nice while you were gone and we would love to see it
back that way. you have already suckered a few newbies since your
untimely return. it has to stop.
uri
--
Uri Guttman --------- uri@sysarch.com ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
------------------------------
Date: Sun, 21 Jan 2001 23:40:20 GMT
From: Uri Guttman <uri@sysarch.com>
Subject: Re: Words in Perl - Pulling Hair
Message-Id: <x74rysxymz.fsf@home.sysarch.com>
>>>>> "S" == Sterling <smullett@omeninc.com> writes:
S> Martien Verbruggen wrote:
>>
>> Well, no, I didn't :) That's why I asked what it was, and why I couldn't
>> find anything about it in the perl documentation :)
>>
>> *grin*
>>
>> Martien
S> I think he was referring these questions at me. Since I also got an
S> email of this post. 8^)
you are correct!
:)
S> In my own defense, I'm an idiot. I did not fully understand the
S> page or the accompanying source code as perl is not my life, my
S> blood, my soul. I shall endeavor to fully explore all avenues of
S> approach on all matters relating to Perl before posting in the
S> future.
don't be so hard on yourself. consider is a learning experience. just
remember that the only builtin operations of perl are all documented in
its docs. don't think any web stuff (unless it is just hmtl'ed versions
of the docs) cover unknown features. since you couldn't find it in the
perl docs, it isn't built in.
as for being an idiot, our stupid troll, moronzilla is back. you can't
claim that title as long as she is around. pray she gets bored and
leaves again, this time for good.
uri
--
Uri Guttman --------- uri@sysarch.com ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
------------------------------
Date: 16 Sep 99 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 16 Sep 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.
| NOTE: The mail to news gateway, and thus the ability to submit articles
| through this service to the newsgroup, has been removed. I do not have
| time to individually vet each article to make sure that someone isn't
| abusing the service, and I no longer have any desire to waste my time
| dealing with the campus admins when some fool complains to them about an
| article that has come through the gateway instead of complaining
| to the source.
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 114
**************************************
