[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev identifying config/version info
From: |
Larry W. Virden |
Subject: |
Re: lynx-dev identifying config/version info |
Date: |
Tue, 23 Feb 1999 07:33:14 -0500 (EST) |
From: Henry Nelson <address@hidden>
> "[2]compile time options". From the users point of view,
> however, this is distractive junk that should not be included
> in a production distribution, i.e., by default it should not
> be compiled in, or it should be stripped out at release time.
> Same as with ALL trace code, IMHO. Don't get me wrong; it's
Boy, I couldn't disagree more - in my opinion, the 'users' are the
ones who need it the MOST. A developer will know about trace and
makefiles, etc. and seldom will need the info provided by these
features. However, a user, particularly on a large system where
they don't even know who built lynx ,are the ones who need this info
when reporting problems.
--
Larry W. Virden <URL: mailto:address@hidden>
<URL: http://www.purl.org/NET/lvirden/> <*> O- "No one is what he seems."
Unless explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
- lynx-dev identifying config/version info, Laura Eaves, 1999/02/18
- Re: lynx-dev identifying config/version info, Laura Eaves, 1999/02/18
- Re: lynx-dev identifying config/version info, dickey, 1999/02/18
- Re: lynx-dev identifying config/version info, Henry Nelson, 1999/02/23
- Re: lynx-dev identifying config/version info,
Larry W. Virden <=
- Re: lynx-dev identifying config/version info, dickey, 1999/02/23
- Re: lynx-dev identifying config/version info, Henry Nelson, 1999/02/23
- Re: lynx-dev identifying config/version info, Henry Nelson, 1999/02/24