Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: Weird directories in scripts (was Re: Setting your system time)
Message-ID: <1990Sep14.211625.756@iwarp.intel.com>
Date: 14 Sep 90 21:16:25 GMT
References: <1990Sep13.183429.17002@uvaarpa.Virginia.EDU> <15856@bfmny0.BFM.COM>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 26
In-Reply-To: tneff@bfmny0.BFM.COM (Tom Neff)

In article <15856@bfmny0.BFM.COM>, tneff@bfmny0 (Tom Neff) writes:
| In article <1990Sep13.183429.17002@uvaarpa.Virginia.EDU> worley@compass.com writes:
| >I've written the following script ...
|  ...
| >do "/compass/c/worley/perl-3.0/lib/getopt.pl";
| 
| >do "/compass/c/worley/perl-3.0/sys/syscall.h";
| 
| Come on people -- is it really necessary to leave this kind of line in a
| Perl script being distributed to the world?  How about exercising a
| little reasonability when you post, and eliminating the weird custom
| directories instead of making thousands of individual users do it?

And replace them with *what*?  *Your* custom directory?  How will
I know what that is?

At least with a name like /compass/c/worley/blah/blah/blah, I know
enough to think "hey, maybe he's *not* talking about something from
the distribution there".

require "/local/merlyn/bin/perl/japh.pl"; &japh(17); # :-)
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/