lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV One way to get rid of memory leaks in Lynx


From: Jason F. McBrayer
Subject: Re: LYNX-DEV One way to get rid of memory leaks in Lynx
Date: 22 Mar 1998 16:56:20 -0600

>>>>> "a" == afn06760  <address@hidden> writes:

a> It seems to me that, rather than use malloc and FREE so freely,
a> lynx developers might consider adding HTDOS.c to the Unix sources,
a> with the idea that the two static buffers in HTDOS.c could be
a> exploited by parts of the lynx code that need to use 1KB of memory,
a> then discard same.  The details of the HTDOS.c code, with the Dos
a> and Unix pathifying, need not be an obstacle, since it is trivial
a> to disable the pathifying, so that the buffer gets returned
a> untouched.

What Lynx really needs is a HTSystemWWWName(), HTSystemFileName(), and
HTSystemFileNameAppend() that can be run on any generated file names
and will do the Right Thing to pathify them, and avoid all the inline
pathname mangling done now.  There would need to be at least Unix,
VMS, DOS/Win, and EMX definitions for the functions, and maybe a
CygWin version, too.  The idea is that you'd call one function which
would be defined at compile-time to contain the right pathifying code
for your platform.

Fixing memory leaks might be a side effect of this more important
change. 

-- 
+----------------------------------------------------------------+
| Jason F. McBrayer              address@hidden |
| The scalloped tatters of the King in Yellow must hide Yhtill   |   
| forever.                   (R.W. Chambers _The King in Yellow_ |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]