delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/10/20/09:01:54

Date: Sun, 20 Oct 1996 14:41:31 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Alexander V. Lukyanov" <lav AT video DOT yars DOT free DOT net>
Cc: T DOT W DOT Seddon AT ncl DOT ac DOT uk, djgpp AT delorie DOT com
Subject: Re: need advice on djgpp vs. Turbo C
In-Reply-To: <199610201212.QAA10524@video.yars.free.net>
Message-Id: <Pine.SUN.3.91.961020143853.29874O-100000@is>
Mime-Version: 1.0

On Sun, 20 Oct 1996, Alexander V. Lukyanov wrote:

> I meant quite that. Huge pointers was introduced to handle huge
> structures, and since library functions can't handle them what's the
> use of huge pointers? read,write,memcpy etc have to be rewritten with
> huge pointers to allow normal using of huge arrays.

It's really not that scary.  Read/write need to be handled in chunks of 
64KB anyway since DOS cannot grok more than that.  Since memcpy expands 
into inline code, I think it will work with huge pointers.  But most 
library functions don't move around buffers, so you don't need to rewrite 
libc.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019