Xref: utzoo comp.lang.c:27791 comp.unix.xenix:11034
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!sco!rogerk
From: rogerk@sco.COM (Roger Knopf 5502)
Newsgroups: comp.lang.c,comp.unix.xenix
Subject: Re: pointers - why dosn't this work? (patch level #1)
Message-ID: <4355@scorn.sco.COM>
Date: 11 Apr 90 23:38:25 GMT
References: <23467@mimsy.umd.edu> <23474@mimsy.umd.edu> <4135@scorn.sco.COM> <1990Apr10.181613.5367@utzoo.uucp>
Sender: news@sco.COM
Reply-To: rogerk@sco.COM (Roger Knopf 5502)
Organization: The Santa Cruz Operation, Inc.
Lines: 19


In article <1990Apr10.181613.5367@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>In article <4135@scorn.sco.COM> rogerk@sco.COM (Roger Knopf 5502) writes:
>>strdup(S) automagically does the malloc for you and returns a 
>>pointer to where it duped the string.
>
>Assuming that you have a strdup() function.  It's not particularly standard.

I made the assumption that it was available because I was reading it
in comp.unix.xenix, not noticing the cross-post to comp.lang.c. I
don't know whether its standard or not but it is available in the SCO
libc. Sorry for any confusion this may have caused anybody.

Roger Knopf
SCO Consulting Services
-- 

"His potential clients were always giving him the business."
	--Robert Thornton