[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Re: syntax change
From: |
Henry Nelson |
Subject: |
Re: lynx-dev Re: syntax change |
Date: |
Tue, 2 Mar 1999 09:35:20 +0900 (JST) |
> Depends on where u want the bloat -- configure, lynx.cfg, option
> screen, binary size, source code size/complexity.
^^^^^^^^^^^
Binary size is a relatively straight forward and tangible place to
start. It benefits some, does not harm others.
> Adding a configure-time option would necessitate ugly ifdefs.
Personally, I think code bloat is more "ugly."
> Anyway, the 123[pg][+-] stuff is so small that I doubt it contributes
> more than a drop in the bucket to binary size.
That's what they all say, and that's why so many drops have fallen
in the bucket. It would be wonderful if a precedent were set by
contributers to either modularize? or macrotize? their code so that it
can be backed out easily. Leaving the dirty work to the coordinating
developer is not polite, IMHO.
> so an option in lynx.cfg or .lynxrc isn't necessary, IMO.
Agree, in this case.
__Henry
- lynx-dev Re: syntax change, (continued)
- lynx-dev Re: syntax change, Kim DeVaughn, 1999/03/01
- Re: lynx-dev Re: syntax change, Philip Webb, 1999/03/02
- Re: lynx-dev syntax change - f not g, Klaus Weide, 1999/03/02
- lynx-dev Re: syntax change - f not g, Kim DeVaughn, 1999/03/02
- Re: lynx-dev syntax change - f not g, Philip Webb, 1999/03/02
- Re: lynx-dev syntax change - f not g, Klaus Weide, 1999/03/02
- Re: lynx-dev syntax change - hidden links digression, Klaus Weide, 1999/03/02
- lynx-dev NNN <something-or-nothing> (was: syntax change), Klaus Weide, 1999/03/02
- lynx-dev Re: NNN <something-or-nothing> (was: syntax change), Kim DeVaughn, 1999/03/02
- Re: lynx-dev Re: NNN <something-or-nothing>, Philip Webb, 1999/03/02
Re: lynx-dev Re: syntax change,
Henry Nelson <=
Re: lynx-dev Re: syntax change, dickey, 1999/03/01