Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal L. Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: recv doesn't widen the read in buffer...
Message-ID: <1991Mar25.003625.576@iwarp.intel.com>
Date: 25 Mar 91 00:36:25 GMT
References: <1991Mar24.035130.16585@uvaarpa.Virginia.EDU>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal L. Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 16
In-Reply-To: eichin@milo.mit.edu (Mark W. Eichin)

In article <1991Mar24.035130.16585@uvaarpa.Virginia.EDU>, eichin@milo (Mark W. Eichin) writes:
| 	Shouldn't perl *never* core dump?

To quote from The Book (Glossary, page 411):

	DUMP
		A Perl statement that is one of the many ways to get a
		Perl program to produce a core file.  Most of the other
		ones are undocumented.

print "Just another Perl hacker,"
-- 
/=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: "Intel: putting the 'backward' in 'backward compatible'..."====/