From: jgevaryahu@hotmail.com (Jonathan Gevaryahu)
Subject: [TUHS] History of strncpy
Date: Wed, 23 Jan 2013 19:37:51 -0500 [thread overview]
Message-ID: <BLU0-SMTP2151BBABA96D8058115B46BC7140@phx.gbl> (raw)
In-Reply-To: <CAGg_6+MMAB9pqrMkiD7kd8gGyRYdSDeV9AZ7zaAOC9etO=GP1Q@mail.gmail.com>
I don't know about strncpy but strcmp appears (not under that name but
with identical functionality) in speak.c from 1973ish...
On 1/22/2013 11:03 PM, Nevin Liber wrote:
> On another list I am on, a discussion about the history and purpose of
> strncpy has arisen. The only reference I have found to it is
> <http://lwn.net/Articles/507432/>:
>
> The original reason for strncpy() was when directory names were
> limited to 14 chars. The other two bytes contained the inode number.
> For that particular case, strncpy() worked quite well.
> Is that really the reason it came into being?
>
> Just a bit curious,
> --
> Nevin ":-)" Liber <mailto:nevin at eviloverlord.com
> <mailto:nevin at eviloverlord.com>> (847) 691-1404
>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
--
Jonathan Gevaryahu AKA Lord Nightmare
jgevaryahu at gmail.com
jgevaryahu at hotmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20130123/a87489b2/attachment.html>
next prev parent reply other threads:[~2013-01-24 0:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2013-01-23 17:56 Michael Spacefalcon
2013-01-23 21:08 ` Larry McVoy
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
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=BLU0-SMTP2151BBABA96D8058115B46BC7140@phx.gbl \
--to=jgevaryahu@hotmail.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).