Re: lynx-dev when, where, why "kb/sec"? Any votes for a "simple" Lynx

[dickey]

> Also, please don't think I put any blame on you or anyone else for the 
> growing size.  There has indeed been a great boost in functionality; much 
> more than 5 times.  (Some of it's even my fault, e.g., getting CJK in.) 
I had intended making chartrans optional, but that didn't work out.

(Changing one function for a more general one which doesn't increase code
size, such as LYOptions's form-options code is a Good Thing, however).
  
> > > past (ca. Oct. 1997) about reducing the image size.  
> > ok (in principle).  it'll make the code more complex though, unless 
> > things are hidden away in macros. 
>  
> Could you easily explain, or give an example, of what "hidden away in 
> macros" means?  A reference in a standard text also okay.  Thanks from 
> a novice. 
A couple of examples:

        + the way I cleaned up the clutter in LYOptions.c - moving
          repetitive code into macros.

        + the cleanup of the temporary file handling functions (instead of
          plastering the code with #if VMS/#else/#if DOSPATH/#else/...,
          move structurally-similar stuff into macros or functions.

          (When I'm reading code, a preprocessor line is distracting).

>  
> __Henry 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey