Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
Date: Wed, 5 Dec 2001 15:39:38 +0300
From: egor duda <deo AT logos-m DOT ru>
Reply-To: egor duda <deo AT logos-m DOT ru>
Organization: deo
Message-ID: <17416878469.20011205153938@logos-m.ru>
To: Pavel Tsekov <ptsekov AT syntrex DOT com>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: string.h vs string.h usage
In-Reply-To: <3C0E12BA.3843123E@syntrex.com>
References: <3C0E0C4C DOT 73A1750D AT syntrex DOT com>
 <15915798356 DOT 20011205152138 AT logos-m DOT ru> <3C0E12BA DOT 3843123E AT syntrex DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Wednesday, 05 December, 2001 Pavel Tsekov ptsekov AT syntrex DOT com wrote:

PT> egor duda wrote:
>> 
>> Hi!
>> 
>> Wednesday, 05 December, 2001 Pavel Tsekov ptsekov AT syntrex DOT com wrote:
>> 
>> SUSv2 mandates both <strings.h> and <string.h>
>> 
>> mingw declares strcasecmp() in <string.h> while SUSv2 says it should
>> be in <strings.h>

PT> Afaik str[n]case is and BSD-ism :)

it doesn't matter as long as standard defines it. please note that it
doesn't marked as "obsolete" -- usage of those functions is supposedly
pretty portable.

PT> Btw here is what glibc on redhat 7.1 says.

PT> /* We don't need and should not read this file if <string.h> was already
PT>    read. The one exception being that if __USE_BSD isn't defined, then
PT>    these aren't defined in string.h, so we need to define them here.  */

of course it's up to mingw guys to decide what's the standard they're
trying to comply with. but i suppose SUSv2 is the right way to go
(excluding functions not defined in msvcrt/crtdll.dll, of course)

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19