HDTenEightyP/NetNews huggingface dataset:
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: Perl bug using read
Date: 7 Nov 92 00:13:13 GMT
Organization: NetLabs, Inc.

In article <MERLYN.92Oct29095217@romulus.reed.edu> merlyn@ora.com (Randal L. Schwartz) writes:
: The number and string value of a scalar are held separately.  Ideally,
: every assignment to a string invalidates the number, and vice versa.
: But there have been bugs in the past where the cache was not properly
: blown, and this is probably an example of that.

Bingo.

: Don't expect a patch for 4.035 from Larry on this... He's too deep
: into Perl 5.0, so we'll have a whole new set of bugs to clean. :-)

As it happens, I'd carried this particular bug over.  It'll be fixed in 5.

: (Larry tells me that nearly every line of Perl 5.0 is *new*.)

If you count "heavily munged" as "new"...

Essentially, the tokener is about half munged, the parser is totally new
except for some of the yacc grammar, and the run-time system is an
unrecognizable transmogrification of the old, with maybe 1/3 new code.
So far it actually parses the entire TEST program, and executes the
first 20 lines or so before blowing up.  When I get it back to where
it'll pass the test suite, then I can *really* start having fun.

Larry
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: equal treatment for "bare words?"
Date: 6 Nov 92 02:12:56 GMT
Distribution: na
Organization: NetLabs, Inc.

In article <8709@blue.cis.pitt.edu.UUCP> rm55@cislabs.pitt.edu (Rudolph T Maceyko) writes:
: I should point out that this inconsistency exists for all of the following
: cases:
: 
: die/warn BAREWORD;
: die/warn BAREWORD, "\n";
: die/warn(BAREWORD);
: die/warn(BAREWORD, "\n");
: 
: (all of the above act as if no argument had been passed to die or warn)

It works right in Perl 5:

$ perl
warn HOWDY;
__END__
HOWDY at - line 1.
$ perl
kill HUP, $$;
__END__
Hangup
$

Larry
Newsgroups: comp.lang.perl
From: sjaak@athena.research.ptt.nl (Sjaak Schilperoort)
Subject: curseperl for MSDOS?
Originator: sjaak@athena.research.ptt.nl
Keywords: curses,perl,msdos
Reply-To: J.W.Schilperoort@research.ptt.nl
Organization: PTT Research
Date: Tue, 10 Nov 1992 08:26:43 GMT

I have written a nice 1200 line curseperl application for
administering bird count reports. It currently runs on Unix and
AtariST. I want to share the program with someone who ownes a
MSDOS-machine. I have read the perl FAQ but it doesn't mention a
curseperl for MSDOS. Does it exist?

			Sjaak.
-- 
Sjaak Schilperoort                   J.W.Schilperoort@research.ptt.nl
PTT Research, The Netherlands
Newsgroups: comp.lang.perl
From: ccechk@nuscc.nus.sg (Heng Kek)
Subject: Oracle most wise, ....
Organization: National University of Singapore
X-Newsreader: Tin 1.1 PL4
Date: Tue, 10 Nov 1992 01:42:00 GMT

[Note: not crossposted]

O Mighty Oracle, whose armpits are more fragrant than anything by
Estee Lauder, whose Greatness exceeds all greatness, whose toes I'm
not worthy of smelling (let alone lick), whose profundity of being
baffles the whole community of nobel laureates, whose intestines are
made of diamond-studded, gold-plated, 4-grillion-carat, platinum,
whose tolerance for pathetic grovelling has probably reached its
limit, answer me this:

Why does it take me 5 days to code the same program in C when it
took only half in Perl?


Kek
From: majidi@rwja.umdnj.edu (Masoud Majidi)
Newsgroups: comp.lang.perl
Subject: push/pop and memory management
Date: 12 Nov 92 19:48:04 GMT
Organization: Robert Wood Johnson Medical School, Piscataway NJ

Dear netters,

I have a small perl code whose memory requirement was getting out of
hand. After studying the code for a while I am convinced that push/pop
is not working the way I expected. To prove the point I wrote a small
program which does nothing but pushing and popping from an array:

for (1 .. 10000)
{
	push (@ary, 13);
	pop (@ary);
}

And I checked the memory allocated to this code before and after the
loop. To my surprise there was more 2.5 Meg difference. Even if the pop
calls don't free the space I still don't understand how pushing 10,000
entries can increase the space by 2.5 Megs. I would appreciate it very
much if somebody would explain the above behavior.

Thanks in advance,

Masoud Majidi (majidi@umdnj.edu)
Newsgroups: comp.lang.perl
From: jns@ace.nas.nasa.gov (John N. Stewart)
Subject: [bind] Bind on a Cray
Organization: NAS, NASA Ames Research Center, Moffett Field, California
Date: Tue, 10 Nov 92 23:19:20 GMT
Distribution: usa


Configuration: 6.1.6 nas.29 CRAY Y-MP
Error:         bind: Invalid argument

Code Frag:     bind(DATA, $us) || die "bind: $!\n";


The program is the Perl version of archie, yet the Cray bind doesn't
act differently on a call basis. Has anyone run into this on some
architecture of some type, and could have a clue where the problem
lies? 

Newsgroups: comp.lang.perl
From: gandalf@sabrina.dei.unipd.it (ROBERTO AVANZI)
Subject: Re: Perl on the Mac?
Organization: D.E.I. Universita' di Padova, Italia
Date: Fri, 6 Nov 1992 10:10:19 GMT

In article <140619@lll-winken.LLNL.GOV> busby@phoenix.ocf.llnl.gov (lee e busby) writes:
>Can anyone give me a pointer to find perl for the
>Macintosh?  Sorry if this is a FAQ.  Thanks.
you have two choices
I)     ftp to ftp.maths.tcd.ie ( i believe) and go somewhere, i do not
       remember exactly, but search a little bit, there are no deep 
       directories. there is a port of perl 4.035 with a POSIX library
       for Think C. I do not use it, but i did not have a great impression.
II)    Great is instead and i use it, the MPW port by Matthias Neeracher
       you can find on ftp.msen.com (or nigel.msen.com) in the 
       directory  /pub/mac/perl? or something like that
       there are  the sources with mac differences, additional files,
       gdbm support, limited support for subprocess (1 only, but hey it's
       something) and two binaries: one is an MPW tool and the other
       is a standalone application. I recomment this one. It has also
       neat graphics (look at the cursor, not a beachball but a camel on
       wheels !!!!).
Cheers
Roberto Avanzi
gandals@sabrina.dei.unipd.it (ITALY !!!)
"Those from Italy send you their greetings" (Hebrews 13:24-NIV)
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: Perl on Sun IPX/Sun OS 4.1.2.
Date: 6 Nov 92 19:14:37 GMT
Organization: NetLabs, Inc.

In article <1992Oct30.024843.27573@mcs.kent.edu> jstuart@mcs.kent.edu (Jeff Stuart) writes:
: Also, to Larry and the bunch: in the next release of perl, are there going to
: be hints for SunOS 4.1.? (including 4.1.3)?

I only put in hints under three conditions.

	1) Taking the default answers doesn't work.
	2) Making the default answers work is Too Hard.
	3) Someone drops me the hints.

Larry
Newsgroups: comp.lang.perl
From: mcook@fendahl.dev.cdx.mot.com (Michael Cook)
Subject: Re: Problems with multiple-splitting
Organization: Motorola Codex, Canton, Massachusetts
Date: Tue, 10 Nov 1992 14:15:20 GMT

horst@faui63.informatik.uni-erlangen.de (Horst Luehrsen) writes:


>In article <ELIAS.92Nov4165430@fitz.TC.Cornell.EDU>, elias@fitz.TC.Cornell.EDU (Doug Elias) writes:
>>From: elias@fitz.TC.Cornell.EDU (Doug Elias)
>>Newsgroups: comp.lang.perl
>>Subject: Problems with multiple-splitting

>[stuff deleted]
>>The problem i'm seeing is that the $date string, obtained from the
>>first split, doesn't seem to be itself splittable.  i can't find
>>anything in the Camel Book to lead me to believe that this is
>>verbotten, and it seems perfectly in keeping with what the functions
>>are supposed to be able to do.
>[stuff deleted]

>Verbotten??? 

>	Verboten!!!

>Wenn schon deutsche Wrter, dann auch richtig!

>(If you use german words, spell them correct!)

That's the English spelling, isn't it? :-)
Anyhow, if you're going to use the English grammar, use it correctLY! :-)

Michael.
Newsgroups: comp.lang.perl
From: ckd@eff.org (Christopher Davis)
Subject: Re: scripts should indicate the Perl version (a proposal)
Organization: Electronic Frontier Foundation Tech Central
Date: Tue, 10 Nov 1992 00:44:37 GMT

MC> == Michael Cook <mcook@fendahl.dev.cdx.mot.com> 

 MC> How about this idea: There should be a way to specify in a Perl
 MC> script what version of Perl the script was written for.  Then, as
 MC> new keywords and other non-backwardly-compatible functionality are
 MC> added, old scripts could still likely work correctly.

How about assigning to $]?  That would handle both forward and backward
compatibility issues:

#!/usr/bin/perl -- #-*-Perl-*-

# this script requires 4.0.35
# and might break under 5.0 because it does undocumented bizarrities
# so we'll force it to be compatible

$] = "4.0.35";

This would have an advantage over the traditional behavior of merely
checking $] for the correct version: it would automatically be
compatible.  Older versions (say, 3.0.18) would go out and ftp the
newest package, compile it, and install it.  Newer versions (5.0) could
lobotomize themselves as you suggested.  Everyone would be happy.

print "Just another ",$sarcastic,"perl hacker,";

(The real solution would be not to use lower case unquoted strings, and
trust in Larry not to break anything.  Or hard-code the version, say:
#!/usr/local/bin/perl4.035 -- #-*-Perl-*-)
--
Christopher K. Davis      | ``Usenet seems to run much like the Kif (or,
<ckd@eff.org>   EFF #14   |   for the TV generation, Klingon) high command.
System Administrator, EFF |   Whoever takes action and can be heard wins.''
+1 617 864 0665  [CKD1]   |   --Peter da Silva <peter@ferranti.com>
Newsgroups: comp.lang.perl
From: schan@birch.srg.af.mil (Stephen Chan x4485)
Subject: PERL 4.035 on SCO v3.2
Organization: SRG, Arinc Research Corp., Annapolis, MD
Date: Thu, 12 Nov 92 15:52:41 GMT
Summary: getting fully functional PERL on 386 SCO v3.2
Keywords: sco perl install

	I'm having some problems getting Perl 4.035 up on my machine. The
configure script was amazing (one day, that script will conquer the world), and
its gotten me 95% of the way there.
	But after all the compiles, the final product fails to pass the goto,
split, regexp and big tests. It hangs on the third part of the goto test,
hangs after the 10th test in split, hangs after the 44th regexp test, and I
start to get 'NaN' after the 60th lib/big test.

	Has anyone else out there seen these problems? I'm running SCO v3.2 on
a 33mhz 386, and using the standard compiler. Should I use gcc instead?

	Any help would be most appreciated!
--
	Stephen Chan
	uunet!srg!schan or uunet!srg!schan@uunet.uu.net
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: A Constant Puzzlement
Date: 7 Nov 92 00:31:34 GMT
Organization: NetLabs, Inc.

The "real" answer, as some have surmised, is that cpp macros are
evaluated when interpolated, and not when defined, which amounts to a
crude form of forward reference.  This corresponds more closely to the
semantics of subroutines than it does to variable assignment.  (If the
efficiency of the subroutines is a problem, you can always poke the
value into a variable up near the top of the program.)

Someone said that doing it this way makes h2ph easier.  In actual fact,
it makes it possible.  Divining the consecution of cpp directives without
actually evaluating them in situ is an exercise in undecidability.

Larry
From: tim@maths.tcd.ie (Timothy Murphy)
Subject: Re: Perl on the Mac?
Organization: Dept. of Maths, Trinity College, Dublin, Ireland.
Date: Sat, 7 Nov 1992 14:27:32 GMT

busby@phoenix.ocf.llnl.gov (lee e busby) writes:

>Can anyone give me a pointer to find perl for the
>Macintosh?  Sorry if this is a FAQ.  Thanks.

I ported perl to the Mac, using Think C, a while ago.
I've used it quite a lot since without problems.

It is available from ftp.maths.tcd.ie
in pub/Mac/perl.hqx .
The source (as diffs from the standard source)
is in the subdirectory pub/Mac/perl-4.035 .

A Mac version of patch is also available
in pub/Mac/patch.hqx
with source in pub/Mac/patch-2.0 .
Various other Mac ports of GNU programs 
can be found in the same place.

They all use a small "ThinkCPosix" library
containing various Unix-like functions,
which again can be found in the same place.

-- 
Timothy Murphy  
e-mail: tim@maths.tcd.ie
tel: +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
Newsgroups: comp.lang.perl
From: chare@unilabs.uucp (Chris Hare)
Subject: Re: explanation of the camel book code needed
Keywords: sh csh perl ksh running with shells
Organization: UniLabs Research Group
Date: Fri, 6 Nov 1992 11:31:02 GMT

In article <nrp.721043320@reading> nrp@csug.cs.reading.ac.uk writes:
>chare@unilabs.uucp (Chris Hare) writes:
>
>>On pg 216 of the camel book is a description of how to make perl run from
>>shells which do not support the #! construct.  I need a conscise, word by
>>word, letter by letter explanation, as I'm somewhat lost o how this is
>>interpreted by the shells, and what it all means.
>
>I don't have the camel book (a serious shortcoming, I know) but I assume
>that you're referring to something like the output produced by a2p and s2p:
>
>#!/gnu/bin/perl
>eval 'exec /gnu/bin/perl -S $0 ${1+"$@"}'
>	if $running_under_some_shell;
>
The code in the book actually is
#!perl
eval '(exit $?0)' && eval 'exec perl -S $0 ${1+"$@"}'
& eval 'exec perl -S $0 $argv:q'
if 0;

>OK.  The first line is obviously the #! line.  The next two lines are split
>because shells interpret one line at a time, whereas perl goes to
>semicolons.  The shell comes along and sees the eval line, and executes it.
>This gets the perl program run with all the right arguments, and since it
>contains an exec the shell goes no further, but the eval makes it return
>the exit code produced by the perl program.
Yup.
>
>Now perl comes along and finds the two-line statement, which says "eval
>this if the variable $running_under_some_shell is true".  Since we're at
>the beginning of the program $running_under_some_shell has not been defined
>and so the eval is not performed, and perl goes on with the rest of the
>program.
Yup.
Now what I need is a concise explanation as to this
   eval '(exit $?0)' && eval 'exec perl -S $0 ${1+"$@"}'
   & eval 'exec perl -S $0 $argv:q'
What is perl actually interpreting?  
>-- 
>nrp@csug.cs.reading.ac.uk  \--------------------------------------------------
>----------------------------\ I'm the kinda guy who likes to have
>his own ... special odour.  And that's why I wear ... TUNA FISH SANDWICH!
>
Who was it that said that anyway??

Thanks!

-- 
????                --- It Always works for me! ---                           
Chris Hare, UNIX Scientist                  Preferred : chare@unilabs.org
Just a mild-mannered consultant by day ....
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: $| for stdin?
Keywords: stdin $| and life
Date: 6 Nov 92 20:33:30 GMT
Organization: NetLabs, Inc.

In article <1992Nov4.235759.14315@utagraph.uta.edu> turbo@cse.uta.edu (Chris Turbeville) writes:
: I am looking for some way of clearing standard in before every read.
: You know the stdin counter-part of $|.  I have a large program
: responsable for helping non-unices do unix admin things safely but I
: can't seem to keep it from getting a wrong char occasionally.  If the
: enter key is a little sticky then I get default responses when they may
: have wanted to enter something just because their fingers are a little
: heavy.  Does anyone know of a way to flush stdin up to now (by now I
: mean some point in the code) and then read something so these extra \n's
: won't clutter up the place.  I have tried seeks and all sorts of
: trickery but to naught.
: Thanks in advance
: -Chris

The solution space for this problem is system dependent.  You'll likely
need to play around with ioctl() or fcntl().  Essentially, you either
need some kind of non-blocking read (see FIONBIO for ioctl() or FNDELAY
for fcntl()) or some way of determining beforehand whether a read
*would* block (and avoiding the read if so), such as FIONREAD for ioctl().

Larry
From: mjeffery@reed.edu (Mark Jefferys)
Newsgroups: comp.lang.perl
Subject: Re: Executing required files
Date: 5 Nov 92 06:21:31 GMT
Article-I.D.: reed.1992Nov5.062131.17033
Distribution: comp.lang.perl
Organization: Reed College, Portland, OR

In article <1992Nov05.052448.29379@spillman.uucp> tye@spillman.uucp (E. Tye McQueen) writes:
% jgd@acl.lanl.gov (Jerry G. DeLapp) writes:
% )[...] Is there a reliable way of determining whether a
% )program *is being* required or *is being* directly executed?

% Perhaps an extension:
% 
%         $^R  The name of the file currently being included by
%              "do" or "require".
% 
% would be nice.

A bit redundant, since __FILE__ does most of this already.  I'd like:

    __REQUIRED__  Expands to true if file is currently being required.
    __INCLUDED__  Expands to true if file is currently being included
                   by "do" or "require".


In the meantime, something like:

	if (__FILE__ eq $0) {
		# I'm being run directly.
	} else {
		# I'm being run by require, eval, or do,
		# or some idiot set $0.
	}

Should work pretty well.


Mark
-- 
Mark Jefferys		Internet: mjeffery@reed.edu
Newsgroups: comp.lang.perl
From: cons@mercury.cern.ch (Lionel Cons)
Subject: Perl bug (Floating exception)
Organization: CERN, European Research Center for Particle Physics
Distribution: comp
Date: Thu, 12 Nov 1992 17:04:32 GMT

When I type:
   perl -e '4646464646 % 3'
I get:
   Floating exception (core dumped)

What happens ?

my perl is:

This is perl, version 4.0

$RCSfile: perl.c,v $$Revision: 4.0.1.4 $$Date: 91/06/10 01:23:07 $
Patch level: 10

my OS is: HP-UX A.08.07 A 9000/710
--

Lionel Cons

+------- CERN - European Laboratory for Particle Physics -------+
| E-mail: cons@dxcern.cern.ch                                   |
| Earth-mail: CN/SW/WS, CERN, CH-1211 GENEVE 23, Switzerland    |
| Phone: +41 22 767 49 13              Fax: +41 22 767 71 55    |
+---------------------------------------------------------------+
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: Problems with multiple-splitting
Date: 6 Nov 92 23:32:14 GMT
Article-I.D.: netlabs.1992Nov6.233214.24911
Distribution: comp.lang.perl
Organization: NetLabs, Inc.

In article <ELIAS.92Nov4165430@fitz.TC.Cornell.EDU> elias@fitz.TC.Cornell.EDU (Doug Elias) writes:
: # This next one doesn't do jack, the variables are empty strings.
: # Is there some reason why you can't split something you've just
: # obtained from a split?
: #
:     ($year, $mon, $day) = split(".", $date);

That's being interpreted as

    ($year, $mon, $day) = split(/./, $date);

and the . is matching every character.  Backwhack it.  The first argument
to split is always interpreted as a regular expression currently, except
in the special case of ' '.

Larry
Newsgroups: comp.lang.perl
From: esch@galaxy.xilinx.com (Eric Schemmerling)
Subject: SunOS5.0 help needed
Originator: esch@xilinx.com
Reply-To: esch@galaxy.xilinx.com (Eric Schemmerling)
Organization: Xilinx Inc.
Date: Sat, 7 Nov 1992 08:02:18 GMT


So, I'm quite sure this is a dumb question...

I just got done tryin to compile perl on SunOS5.0

the compile ran with a few warnings,

When I try to run perl I get:

ld.so.1: ./perl: can't find file libucb.so.1


what gives???

should I have done somthin????

Thanks

esch
Newsgroups: comp.lang.perl
From: vanepp@fraser.sfu.ca (Peter Van Epp)
Subject: Re: require "did not return a true value" ???
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Tue, 10 Nov 1992 07:01:30 GMT

lynch@hpcc01.corp.hp.com (Howard Lynch) writes:

>Thanks for all the responses!  This is indeed a generous group of users!

>Hey, Larry, how about putting a note in the next edition of the book about
>the requirement for a require'd file to have a statement in it that causes
>a 'true' to be returned?  Seems like a good thing to be in the book for us
>novices.

>Thanks again to all!

>Howard Lynch
>HP OCD IC Manufacturing
>hl@hpocia.sj.hp.com

Index: library, the standard,389

top of 390:

description of how library files end with 1; to make require succeed, and that
it is necessary that they do so lest the require fail ...


Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada
Newsgroups: comp.lang.perl
From: ckd@eff.org (Christopher Davis)
Subject: Re: Platform information
Organization: Electronic Frontier Foundation Tech Central
	<1992Nov9.163103.24294@nntpserver.chevron.com>
	<1992Nov10.154053.3471@news.eng.convex.com>
Distribution: comp.lang.perl
Date: Tue, 10 Nov 1992 23:50:28 GMT

Tom> == Tom Christiansen <Tom Christiansen <tchrist@convex.COM>> 

 Tom> Yes, that would maybe be nice.  If we use __ARCH__ then we'll 
 Tom> be in trouble with byte-compiled code that gets moved around, 
 Tom> but there's no real precedent for &ARCH either.

$^A perhaps?  (Hey, wonder if assigning to this... hmm...)

#!/usr/bin/perl -- #-*-Perl-*-

# we do a lot of processing, so speed the machine up

$^A = 'cray';

$silly_suggestion++;
__END__
--
Christopher K. Davis      | ``Usenet seems to run much like the Kif (or,
<ckd@eff.org>   EFF #14   |   for the TV generation, Klingon) high command.
System Administrator, EFF |   Whoever takes action and can be heard wins.''
+1 617 864 0665  [CKD1]   |   --Peter da Silva <peter@ferranti.com>
Newsgroups: comp.lang.perl
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Platform information
Originator: tchrist@pixel.convex.com
Date: Tue, 10 Nov 1992 15:40:53 GMT
Distribution: comp.lang.perl
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, Colorado Springs, CO
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of hdnea@usho92.hou281.chevron.com (David Neal):
:Quoth Larry Wall:
:>No, your best bet is probably to run uname -a and try to intuit from there.
:>You might look at how Configure tries to find hints files.
:
:Yes, BUT would it be possible to add such an item?? It would not
:have to be determined dynamically, after all. A compile time
:constant that was in the same variable on each platform would be
:enough: $_!_@#$ or something.

Yes, that would maybe be nice.  If we use __ARCH__ then we'll 
be in trouble with byte-compiled code that gets moved around, 
but there's no real precedent for &ARCH either.

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

You have to admit that it's difficult to misplace the Perl sources.  :-)
		--Larry Wall in <1992Aug26.184221.29627@netlabs.com>
From: filo@pegasus.Stanford.EDU (David Filo)
Newsgroups: comp.lang.perl
Subject: Help with quotes
Date: 5 Nov 92 05:14:06 GMT
Reply-To: filo@pegasus.stanford.edu
Distribution: comp
Organization: Stanford University

I'm having a bit of a problem with quoting.

This works as expected.  It replaces the first character with a double-
quote.

$ perl -pe 's/./sprintf ("\\"")/e; print "<$@>" if $@'
help
"elp
$

Below is the same thing except $& has been added to the sprintf.  In
this case the evaluation of the replacement string fails.  I have not
been able to find a way to properly escape the double-quote to be
printed.

$ perl -pe 's/./sprintf ("$&\\"")/e; print "<$@>" if $@'
help
<EOF in string at (eval) line 1, <> line 1.
>elp
$

I know I could just changes quote characters, but I need a way to
include the quote character inside the quoted string.

Any help on this would be greatly appreciated.

Thanks,

David Filo
filo@pegasus.stanford.edu