From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] History of strncpy
Date: Wed, 23 Jan 2013 13:08:53 -0800 [thread overview]
Message-ID: <20130123210853.GG22032@bitmover.com> (raw)
In-Reply-To: <1301231756.AA27240@ivan.Harhan.ORG>
On Wed, Jan 23, 2013 at 05:56:14PM +0000, Michael Spacefalcon wrote:
> Ronald Natalie <ron at ronnatalie.com> wrote:
> > I suspect strcpy arrived with the "portable I/O library", an abomination
> > that eventually evolved into the stdio library and to this day is still
> > stinking up the standard C language.
>
> What's so bad about stdio? That's a genuine question - I've never had
> a reason to dislike stdio...
Well, there are little incompats that make cross platform unpleasant.
We (bitkeeper source management guys) gave up and imported the NetBSD
stdio library and ship that. Which did enable some fun enhancements.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2013-01-23 21:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:56 Michael Spacefalcon
2013-01-23 21:08 ` Larry McVoy [this message]
2013-01-23 21:39 ` Ronald Natalie
2013-01-23 21:46 ` John Cowan
2013-01-24 6:02 ` Larry McVoy
2013-01-24 6:34 ` Steve Nickolas
2013-01-24 14:42 ` Ronald Natalie
2013-01-24 14:52 ` Warner Losh
2013-01-24 16:01 ` Ronald Natalie
2013-01-24 18:31 ` Tom Ivar Helbekkmo
2013-01-25 2:06 ` Warner Losh
2013-01-24 16:21 ` Clem Cole
2013-02-01 0:28 ` Larry McVoy
2013-01-31 23:52 ` Random832
2013-02-01 0:06 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2013-01-23 4:03 Nevin Liber
2013-01-23 4:41 ` Warren Toomey
2013-01-23 4:58 ` Warner Losh
2013-01-23 14:16 ` Clem Cole
2013-01-23 15:01 ` Ronald Natalie
2013-01-23 15:24 ` Armando Stettner
2013-01-23 17:49 ` scj
2013-01-23 18:19 ` Ronald Natalie
2013-01-23 19:33 ` Ronald Natalie
2013-01-23 19:59 ` Clem Cole
2013-01-23 22:43 ` Mary Ann Horton
2013-01-24 0:01 ` Clem Cole
2013-01-24 0:37 ` Jonathan Gevaryahu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130123210853.GG22032@bitmover.com \
--to=lm@bitmover.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).