Groups | Search | Server Info | Login | Register

Groups > comp.lang.pascal.borland > #188

Re: Why did Turbo Pascal implement its own heap manager?

Show all headers | View raw

On 2017-02-08, Jim Leonard <MobyGamer@gmail.com> wrote:
> The only possible reason I can think of is that Borland's management only
> uses 8 bytes of overhead instead of DOS's 16 bytes per overhead (per MCB),
> so I guess the advantage was that you could use 8 less bytes per
> allocation, and also allow a minimum allocation of 8 bytes instead of
> DOS's 16 bytes.  

Or something requiring control in e.g. overlays ?

Back to comp.lang.pascal.borland | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Why did Turbo Pascal implement its own heap manager? Jim Leonard <MobyGamer@gmail.com> - 2017-02-08 15:31 -0800
  Re: Why did Turbo Pascal implement its own heap manager? "Gene Buckle" <gene.buckle@bbs.retroarchive.org.remove-101r-this> - 2017-02-14 14:17 -0800
    Re: Why did Turbo Pascal implement its own heap manager? Jim Leonard <mobygamer@gmail.com> - 2017-03-08 08:49 -0800
  Re: Why did Turbo Pascal implement its own heap manager? Marco van de Voort <marcov@toad.stack.nl> - 2017-03-09 09:22 +0000
  Re: Why did Turbo Pascal implement its own heap manager? sillyluis <sillyluis@gmail.com> - 2017-03-14 10:31 -0700

csiph-web