Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <20011205203624.36458.qmail@web14508.mail.yahoo.com> Date: Thu, 6 Dec 2001 07:36:24 +1100 (EST) From: =?iso-8859-1?q?Danny=20Smith?= Subject: mingw-clingons [Was: Re: string.h vs string.h usage] To: cygwin-apps AT cygwin DOT com In-Reply-To: <20011205132851.GB17608@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit --- Christopher Faylor wrote: > On Wed, Dec 05, 2001 at 03:39:38PM +0300, egor duda wrote: > > I can't believe that I've woken up to a huge thread about this trivial > issue. > > Can't we just rename strings.h to string.h in setup sources? What's the > big frigging deal here? > > Why does every thread that touches setup.exe have to be so torturous? > > cgf I've just thought of a new email virus, One starts a discussion about some trivial issue on three developer lists simultaneously (it's best to pick lists that like to be pedantic). Soon the whole world grinds to a stop. Apart from above, I have no concerns with a do-nothing strings.h. Please, however, refrain from adding in sys/params.h, sys/resource.h, termio.h, etc. The ACT distro of mingw did that and it means that much code written for the ACT version (including the code needed to build the gnat compiler) needs surgery to get rid of unprotected #include , etc that aren't really needed on mingw after all. Danny http://shopping.yahoo.com.au - Yahoo! Shopping - Free CDs for thousands of Priority Shoppers!