TIP: Click on subject to list as thread! ANSI
echo: aust_c_here
to: Andrew Clarke
from: Frank Adam
date: 1996-06-16 23:42:00
subject: free()

G'Day Andrew,
 
-=> Quoting Andrew Clarke to Frank Adam <=-

 > What i would like to know now is, if the allocated size of the array 
 > ptr points at can be determined in some way.
 AC> Yes, probably with some sort of code (that would be hidden to the
 AC> user) to  record the size of the memory allocation along with the 
 AC> location of the pointer itself and add it to a linked-list 
 AC> of structs.  Each time your custom memory allocation 
 AC> routine was called, the code would execute.  Memory 
 AC> reallocation and deallocation would then modify the linked-
 AC> list and records of data sizes therein, as appropriate. 
Yep, got that already :-)

 AC> This is probably pretty much how most (all?) standard C 
 AC> library memory allocation routines work (no doubt each 
 AC> compiler has its own implementation and storage layout 
 AC> though).
That's what i'm afraid of.

 AC> I hope that's not too vague.  :-)  What you ask can 
3-4 years ago printf was vague, who knows what another 3 years can bring.
:-)  

 AC> certainly be done, but would take some time and effort.  So 
 AC> I'll leave the fun part up to you. 
Of course, let the newbies do the dirty work..
 
 > While i got you, is vidmanager on the net yet ? 
 AC> No, not yet.  In your words, I "may have to write a program
for it". 
 AC> :-) 
Heheh, but my function is useless, anyone looking at VidMgr should see 
it's merits and capabilities, without too much explanation. 
Oh btw, i've found it. Serves me right putting it under libs\vidmgr\ :-)

 AC> which suprised me initially, but given the relatively high 
 AC> number of requests for VidMgr reposts in C_ECHO since I 
 AC> I never expected such a high demand for the library!  I
I think it's the first time that anyone released a complete text video 
library AND source, most of the time they come in .libs, which
as far as i'm concerned leaves me without a chance to fix potential bugs
in them.
Bgiobj30 and a re-write of four weeks work comes to mind.:-(
                  
Ps: Sorry, had to cut a "small" part of your mssg. 
Got a bit dirty, while it was dragging on the floor !! ;-)
                               

  L8r Frank (fadam{at}ozemail.com.au).
  

--- Maximus 3.01
* Origin: The Software Parlour (3:635/544)
SEEN-BY: 50/99 620/243 623/630 632/349 635/503 544 727 711/401 409 410 413
SEEN-BY: 711/430 808 809 932 934 712/515 713/888 714/906 800/1
@PATH: 635/544 50/99 711/808 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.