Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Hans-Peter Diettrich Newsgroups: comp.lang.forth Subject: Re: Importing from wordlists. Date: Sat, 04 Apr 2015 16:48:42 +0200 Lines: 14 Message-ID: References: <5517f359$0$23216$e4fe514c@dreader34.news.xs4all.nl> <9dx7nwf774mu$.jd50glhc7mu2$.dlg@40tude.net> <2015Apr3.233709@mips.complang.tuwien.ac.at> <2015Apr4.153059@mips.complang.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 8ZZbETA3HFCGu8GyYAXu/Al3Dvrk1o9u34Rrxu2a4Aa/Qrkc0e Cancel-Lock: sha1:Fz/R3a7rCp37TQUv8OcvnNXNUhI= User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <2015Apr4.153059@mips.complang.tuwien.ac.at> Xref: csiph.com comp.lang.forth:37951 Anton Ertl schrieb: > The way a file buffer is handled in an editor is certainly a > fundamental design decision. GNU Emacs loaded the whole file into RAM > early on (long before there was a 64-bit port), which increases the > footprint, but simplifies the implementation. EMACS = Eight Megabytes Almost Continuously Swapping ;-) You are right, every application should be aware of systems with little RAM, or of big files exceeding physical RAM. This has been true for 16 and 32 bit address space, and still is true for 64 bit address space. DoDi