Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!ltuxa!we53!sw013b!dj3b1!killer!tad
From: tad@killer.UUCP (Tad Marko)
Newsgroups: net.lang.c
Subject: Re:  Header file strings.h
Message-ID: <240@killer.UUCP>
Date: Sun, 22-Jun-86 20:11:49 EDT
Article-I.D.: killer.240
Posted: Sun Jun 22 20:11:49 1986
Date-Received: Wed, 25-Jun-86 04:15:05 EDT
References: <1434@brl-smoke.ARPA>
Organization: The Unix(tm) Connection BBS, Dallas, Tx
Lines: 32
Summary: I think string.h is the same thing(?)

In article <1434@brl-smoke.ARPA>, drears@ardec.arpa (FSAC) writes:
> Paul Schauble writes:
> 
>>I am trying to port a program from Unix to MS-DOS.  It makes use of a
>>header file <strings.h>.  This is not supplied with Microsoft C.  Could
>>someone please enlighten me as to what this contains?
> 
>    <strings.h>  contains the data types for the string
> operations - strcat, strncat, strtok, strcpy, etc.  I have used the
> strings functions many times without using this header file.  If
> you are checking the return codes of the functions explicitly define
> the functions.  Example:
> 
> char *strcat(), *strcmp();
> int strlen;
> 
>    I believe Microsoft C libraries contains the string functions. In
> that case just explicitly define the functions. If they don't  you might
> have to write the string functions yourself.

I use the functions quite often, but the header file for MSC is string.h.
I recently ported a program from MSC to an NBI 4044 running 4.2BSD, and the
only change necessary was to change 

#include <string.h>

to

#include <strings.h>

everything worked fine after that.  Perhaps this and several other MSC 
differences are the result of it complying to the new ANSI C standard?