This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: string.h vs string.h usage


On Wed, Dec 05, 2001 at 03:39:38PM +0300, egor duda wrote:
>Hi!
>
>Wednesday, 05 December, 2001 Pavel Tsekov ptsekov@syntrex.com wrote:
>
>PT> egor duda wrote:
>>> 
>>> Hi!
>>> 
>>> Wednesday, 05 December, 2001 Pavel Tsekov ptsekov@syntrex.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.

mingw doesn't have to adhere to this standard!

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]