Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!eternal-september.org!feeder.eternal-september.org!news.stack.nl!.POSTED!not-for-mail From: Marco van de Voort Newsgroups: comp.lang.pascal.borland Subject: Re: Memory, objects, and TCollections Date: Wed, 25 Jul 2012 12:10:12 +0000 (UTC) Organization: Stack Usenet News Service Lines: 13 Message-ID: References: <45fb5804-296d-43f4-bd0d-ec3d109a5d27@y12g2000yqe.googlegroups.com> <7efa8ee5-eb59-4232-ba0e-c648a2a96a9a@z19g2000vbe.googlegroups.com> NNTP-Posting-Host: toad.stack.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: mud.stack.nl 1343218212 78363 2001:610:1108:5010::135 (25 Jul 2012 12:10:12 GMT) X-Complaints-To: abuse@stack.nl NNTP-Posting-Date: Wed, 25 Jul 2012 12:10:12 +0000 (UTC) User-Agent: slrn/0.9.9p1 (FreeBSD) Xref: csiph.com comp.lang.pascal.borland:114 On 2012-07-23, Jim Leonard wrote: > On Jul 22, 4:07?pm, Marco van de Voort wrote: >> Basically all I can think of is using upper memory blocks (since the limit >> is 1MB not 640k) and (data) overlays. > > You can use overlays for data? Same principle. Code overlay is based that some code is only needed at certain times. One can do the same for data, page data into the EMS pageframe when needed. This is mostly explicit though. (iow you have the responsibility to do it at the same time). XMS and EMS arrays are more or less based on this.