[Top][All Lists]

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

Re: lynx-dev valgrind

From: Leonid Pauzner
Subject: Re: lynx-dev valgrind
Date: Fri, 14 Feb 2003 14:21:55 +0300 (MSK)

14-Feb-2003 10:03 Henry Nelson wrote:
>> I mean that "#ifndef DONT_TRACK_INTERNAL_LINKS" string is removed from the
>> two files (was done partially in dev.10 and now finished). So this code is a
>> mainline and is available both for "--enable-internal-links" and

> Thanks for the clarification.

>> The logic of these two files is clearly understood by me now, and I think

> It's always been very foggy to me.  I thought that "--enable-internal-links"
> and "DONT_TRACK_INTERNAL_LINKS" were mutually exclusive, or at least that

> enabling the configure option turned OFF the define.  Removing "#ifndef
> DONT_TRACK_INTERNAL_LINKS" seems to in effect make the "--enable-internal-
> links" configure option the default, or more correctly the "mainline" code
> and not an "option" anymore.  (Should be removed from the configure script,
> and references to it removed from installation and help documentation?)

No, again.  "#ifndef DONT_TRACK_INTERNAL_LINKS" was removed from TWO files.
The rest (and most) "internal links" code left ifdefed as it was before, so
both --enable-internal-links and --disable-internal-links configure options
have the same meaning as before.

>> may work poperly without "internal links"). Read Klaus notes if you have a
>> strong interest.]

> Very "strong interest" but not enough brain power!  I take all of this to

I add a reference to the old changes2.8
Contrary to ideas, the implementation is rather hairy.

> mean that Klaus' logic has finally been adopted unequivocally.

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

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