Ordering dependency between string.h and strings.h.

Christian MICHON christian.michon at gmail.com
Sat Dec 23 08:20:23 UTC 2006


sorry for top posting.

the scope of my answer was not on SUSv3 (I do not have this
system at hand). Most of what I recalled was for sun/solaris,
when some functions (truly deprecated now) where still
sitting only in strings.h

at the end of this paragraph, you still state the
same thing: including string.h is the right thing to do.

On 12/23/06, Rich Felker <dalias at aerifal.cx> wrote:
> Your reply is incorrect anyway, and please don't top-post. string.h is
> the ANSI/ISO C header with the standard functions. strings.h existed
> on various odd legacy systems and it's the place to which SUSv3 has
> relegated various deprecated and legacy functions which should not be
> used. There is nothing wrong with including both strings.h and
> string.h (except that you probably shouldn't be using the functions in
> strings.h at all...).

-- 
Christian



More information about the uClibc mailing list