Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Joe Buehler Subject: Re: Beginnings of a patch: /etc/hosts Date: Thu, 12 Sep 2002 11:48:52 -0400 Lines: 15 Message-ID: References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020911162837 DOT 02a7c438 AT pop3 DOT cris DOT com> <20020912005439 DOT GB8834 AT redhat DOT com> NNTP-Posting-Host: hekimian.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1031845721 13130 206.205.138.10 (12 Sep 2002 15:48:41 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Thu, 12 Sep 2002 15:48:41 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en Christopher Faylor wrote: > I agree with this, especially in this case. If a user casually changes > an environment variable to something "nonstandard" then they shouldn't > be surprised by the behavior of our tools. This is different from > prompting them for OS and letting the user lie if they want to. In > that case, I'd agree that they should be able to do this. Environment variables are the source of a lot of trouble, and I avoid them as much as possible. What a great idea -- global variables in your program that any user can change -- regardless of whether he knows he did it, or what the effect might be! Joe Buehler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/