[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev dev17 clue?
From: |
posterkid |
Subject: |
Re: lynx-dev dev17 clue? |
Date: |
Wed, 17 Feb 1999 17:50:54 -0800 |
[replying via web archive, sorry no In-Reply-To:]
> * From: Philip Webb <address@hidden>
> * Date: Wed, 17 Feb 1999 19:19:15 -0500 (EST)
> _________________________________________________________________
>
>i meant to comment that the stripped binary of 2-8-2dev.17 is 1,59 M
>a/a 2-8-1rel.1 , which is 1,45 M : might the problem have anything
>to do with the .po stuff, which i paid no attention to? anyway, it's bigger.
I think I would like to create a configure option to disable all of
the extended cookie options that have recently been created, from
COOKIE_ACCEPT_DOMAINS to this latest configuration of cookie validity
checking. Before I sift through the #ifdef soup (I like that line),
does anyone have issues/arguments against more compiletime options?
Perhaps it should even default to be disabled -- I expect several
people are happy with the cookie behavior as it was before. I have
the nasty feeling we're adding bloat with some of this stuff.
-bjp
--
no sig
- lynx-dev dev17 clue?, Philip Webb, 1999/02/17
- Re: lynx-dev dev17 clue?,
posterkid <=
- Re: lynx-dev dev17 clue?, Henry Nelson, 1999/02/22
- Re: lynx-dev dev17 clue?, dickey, 1999/02/23
- Re: lynx-dev dev17 clue?, dickey, 1999/02/23
- Re: lynx-dev dev17 clue?, Bela Lubkin, 1999/02/23
- Re: lynx-dev dev17 clue?, Henry Nelson, 1999/02/23