Date: Fri, 19 Feb 2010 22:46:37 -0600 From: "Karl O. Pinc" References: <4B7F1AAA.5090103@...1114...> <1266637180.23846.1@...1207...> In-Reply-To: <1266637180.23846.1@...1207...> (from kop@...1206... on Fri Feb 19 21:39:40 2010) Message-Id: <1266641197.32062.0@...1207...> MIME-Version: 1.0 Subject: Re: [Openvpn-devel] [PATCH v2] Do not randomize resolving of IP addresses in getaddr() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: openvpn-devel@lists.sourceforge.net On 02/19/2010 09:39:40 PM, Karl O. Pinc wrote: > If someone who explicitly chooses a functionality > needs to get a warning about the default they > should get this warning at ./configure time -- > the time they make the choice.=20 The only time I can think of that a warning should be delivered to those who explicitly choose functionality in the process of deprecation is to, _after_ the default has changed, deliver a ./configure time warning to those who explicitly choose the default telling them that they no longer have to be explicit because they are choosing what is now the default. It hardly seems worth it. Karl Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein