home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!decwrl!pa.dec.com!nntpd2.cxo.dec.com!nntpd.lkg.dec.com!tkou02.enet.dec.com!jrdzzz.jrd.dec.com!jrd.dec.com!doi
- From: doi@jrd.dec.com (Hitoshi Doi)
- Newsgroups: comp.lang.perl
- Subject: Re: Perl and low-memory environments
- Message-ID: <Bs4Itn.28v@jrd.dec.com>
- Date: 29 Jul 92 00:03:23 GMT
- References: <1992Jul28.164057.14549@Princeton.EDU>
- Sender: usenet@jrd.dec.com (USENET News System)
- Organization: DEC Japan Research and Development Center
- Lines: 32
- Nntp-Posting-Host: usagi.jrd.dec.com
-
- In article <1992Jul28.164057.14549@Princeton.EDU>, rjc@onion.princeton.edu (Raymond Chen) writes:
- # Although perl was written for 32-bit virtual memory UNIX boxes,
- # many of us use it on 16-bit low-memory machines like IBM PC's.
- # (Beyond spec, I know, but hey.)
-
- You can run 32 bit programs if your PC is a 386:-)
-
- # I'm wondering if any of my MS-DOS brethren have any space-saving
- # tips to share. I'm already using the following tricks:
- #
- # - Use the symbol table as an associative array.
- # - Don't load subroutines until they're needed.
- # - Discard subroutines when they're no longer needed.
-
- How's the performance with these tricks?
-
- # But that's still not enough. I'm thinking of moving all of main
- # into subroutines so that I can discard bits and pieces of main as
- # they are no longer needed.
- #
- # Has anyone had experience tuning code for low-memory machines?
-
- I tried, and failed. Some of my perl programs are just too big to
- even load up on MS-DOS. I get "out of memory" before it even runs.
- So I built perl with DJGPP.
-
- One thing that helped a little (or it could have been my imagination)
- is to not use local() variables.
- --
- Hitoshi Doi, International Open Systems Engineering doi@jrd.dec.com
- Japan Research and Development Center decwrl!jrd.dec.com!doi
- Digital Equipment Corporation Japan [from Japan: doi@dec-j.co.jp]
-