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 Message-ID: From: Heribert Dahms To: "'Robert Collins'" , "'Kilroy, David'" , cygwin AT cygwin DOT com Subject: RE: Re[3]: cygwin download incomplete - try again - loop? Date: Fri, 7 Jun 2002 22:12:21 +0200 MIME-Version: 1.0 Content-Type: text/plain Hi Rob, unless I lost track in the thread, wouldn't rfc1738 simply need to check right at the beginning something like if (!ptr || !*ptr) return ptr; and how many million times does setup call it that it makes a noteable difference to the user? Or do you re-install cygwin hundred times a day 8-) Bye, Heribert (heribert_dahms AT icon-scm DOT com) > -----Original Message----- > From: Robert Collins [SMTP:robert DOT collins AT syncretize DOT net] > Sent: Friday, June 07, 2002 17:11 > To: 'Kilroy, David'; cygwin AT cygwin DOT com > Subject: RE: Re[3]: cygwin download incomplete - try again - loop? > > > On Behalf Of Kilroy, David > > > In my opinion, the rfc1738 code should be fixed so it doesn't > > choke on null > > or empty strings (which I think is reasonable), and then you > > don't need > > special code to identify your local cache. > > Yes but.... The rfc1738 code is ok, it's the C++ classes that > are choking, and fixing them is a little harder. Adding overhead to > rfc1738 is not good either though :[. > -- 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/