Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Date: Wed, 5 Dec 2001 16:06:16 +0300
From: egor duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.53 RC/4)
Reply-To: egor duda <cygwin-apps AT cygwin DOT com>
Organization: deo
X-Priority: 3 (Normal)
Message-ID: <13918476397.20011205160616@logos-m.ru>
To: cygwin-apps AT cygwin DOT com
Subject: Re: string.h vs string.h usage
In-Reply-To: <3C0E1592.BE4AA60@yahoo.com>
References: <3C0E0C4C DOT 73A1750D AT syntrex DOT com>
 <15915798356 DOT 20011205152138 AT logos-m DOT ru> <3C0E1592 DOT BE4AA60 AT yahoo DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Wednesday, 05 December, 2001 Earnie Boyd earnie_boyd AT yahoo DOT com wrote:

EB> egor duda wrote:
>> Wednesday, 05 December, 2001 Pavel Tsekov ptsekov AT syntrex DOT com wrote:
>> SUSv2 mandates both <strings.h> and <string.h>

EB> Wrong documentation base.  You must use MSDN for MinGW.

why? i can understand this wrt w32api, but for c runtime?

correct me if i'm wrong, but i was thinking that mingw is basically a
"portability toolkit" just like cygwin, with only difference that it
doesn't possess "portability layer" and uses native dlls.

that said, when i port some program that's written "portably" in the
sense "complies with SUSv2", i suppose that it'd be ported without
much fuss, if it doesn't use functions not provided by crtdll/msvcrt.

the problem with -mno-cygwin here is that afaics there's no easy way
to prevent gcc from looking into standard places when it's looking for
headers. with "true" native mingw gcc everything's ok. but when we use
cygwin gcc with -mno-cygwin, and application includes <strings.h>, gcc
will include cygwin's header. it'd give no warnings or errors until it
comes to linking and we'll see a bunch of "__impure_ptr" undefined.

>> mingw declares strcasecmp() in <string.h> while SUSv2 says it should
>> be in <strings.h>
>> 
>> i believe mingw headers should be fixed/updated.

that is, if mingw doesn't really provide any of the functions declared
in <strings.h> (a quick look at msvcrt/crtdll exports made me think it
doesn't), it may just provide an empty one. it'd solve
-mno-cygwin problems and won't break anything in mingw world.

EB> No, MinGW headers are correct according to MSDN.  Perhaps the problem
EB> here is that strcasecmp doesn't exist in the MinGW world.

then it's not clear to me why it's declared in mingw's <string.h>

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