delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2001/11/08/06:21:16

From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: sizeof void* ?
Date: 8 Nov 2001 11:09:59 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 16
Message-ID: <9sdp67$fki$1@nets3.rz.RWTH-Aachen.DE>
References: <Xns91533B07D431Braf256civ AT 193 DOT 219 DOT 28 DOT 2>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1005217799 16018 137.226.32.75 (8 Nov 2001 11:09:59 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 8 Nov 2001 11:09:59 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Raf256 <raf256 AT go2 DOT pl> wrote:

> how can I here check current size of memory block that begins in ptr ?

Best if you don't do it at all.  It would make your program limited to
a single version of a single programming toolchain, as you'ld have to
look into details considered private to the implementation of
malloc().

If you need that value, remember it in your program.  Anyway: what
would you need the previous size of the array for, in a realloc()
call? You're just modifying that size anyway, so why bother what it
was before?
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


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