Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!xanth!nic.MR.NET!hal!ncoast!allbery
From: allbery@ncoast.ORG (Brandon S. Allbery)
Newsgroups: comp.sources.d
Subject: Re: Perl Question
Message-ID: <13559@ncoast.ORG>
Date: 12 Apr 89 02:16:58 GMT
References: <658@ndcheg.cheg.nd.edu>
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: comp.sources.d
Distribution: na
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 24

As quoted from <658@ndcheg.cheg.nd.edu> by kellow@ndcheg.cheg.nd.edu (John Kellow):
+---------------
| get a core dump.  The README file says that Perl probably won't work
| on machines with a small address space.  Now my question:  Just how small
| is small?  I have a SYSV.2 machine(68010 based) with 1.5M of physical memory 
| and a 3.0M virtual address space, is this sufficient?  Has anyone ran Perl
+---------------

3B1, I presume....  ;-)

I've got perl up on ncoast; aside from a few compiler bugs that had to be
worked around, it works fine -- if agonizingly slow.  Ncoast has 2MB of
physical memory, 1.7MB of which is available to user processes (System III;
no demand paging).

The comment about small address spaces applies primarily to 80286 Unix/Xenix
boxes; Perl can manipulate objects of size > 64K, so segments are a lossage.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@ncoast.org
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
      Send comp.sources.misc submissions to comp-sources-misc@<backbone>
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser