From: Russ Cox <rsc@swtch.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] irc answers - man and memmove
Date: Mon, 5 Dec 2005 07:07:25 -0500 [thread overview]
Message-ID: <ee9e417a0512050407w7a2893d1of70d55dae332df87@mail.gmail.com> (raw)
(Sorry, don't have email addresses for these people.)
sretzki interesting, one of the biggest problems I have with
plan9 is that functions in manpages are handled as
normal words, instead of e.g. postfixing every function
with ()
but I guess that is just me and personal taste
fgb ah, yes
I think it's because the manuals are intended to be
printed too
sretzki Well, it is not that awfull, most times, it is clear.
There is no such English word like "alloctree". Just
that they are capitalized at the start of sentences,
but you look at the prototype at the beginning of the
manpage, anyway
it becomes interesting if the function is a valid English
word, like "respond" in 9p(2) :)
If you read the pages with man -P, which shows you the typeset
version, these names will be in italics, which should make them
easier for you to recognize as function names. The manual is,
as fgb and man(1) point out, intended to be typeset.
equuelus which file(s) do i need to include when i want to use
memcpy in the kernel, tried #include "libc.h", but
that didn't work. anyideas?
Use memmove instead, which has the same definition on all systems.
See memory(3):
BUGS
ANSI C does not require memcpy to handle overlapping source
and destination; on Plan 9, it does, so memmove and memcpy
behave identically.
Russ
next reply other threads:[~2005-12-05 12:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 12:07 Russ Cox [this message]
2005-12-05 19:07 ` Sascha Retzki
2005-12-06 1:09 ` Paul Lalonde
2005-12-06 1:14 ` Rob Pike
2005-12-06 1:17 ` Paul Lalonde
2005-12-06 1:48 ` Russ Cox
2005-12-07 9:57 ` Gorka guardiola
2005-12-07 10:41 ` Lucio De Re
2005-12-06 1:22 ` erik quanstrom
2005-12-06 6:31 ` [9fans] Capitalization in man pages Lyndon Nerenberg
2005-12-06 7:01 ` Rob Pike
2005-12-06 9:44 ` Charles Forsyth
2005-12-06 11:01 ` Lyndon Nerenberg
2005-12-06 11:17 ` Charles Forsyth
2005-12-06 11:27 ` Lyndon Nerenberg
2005-12-06 11:12 ` Lyndon Nerenberg
2005-12-06 11:18 ` Lucio De Re
2005-12-06 12:22 ` Lyndon Nerenberg
2005-12-06 12:32 ` Charles Forsyth
2005-12-06 12:40 ` Lyndon Nerenberg
2005-12-06 13:02 ` Lyndon Nerenberg
2005-12-06 13:41 ` Charles Forsyth
2005-12-06 13:54 ` Lyndon Nerenberg
2005-12-06 14:30 ` John Stalker
2005-12-06 18:11 ` Charles Forsyth
2005-12-06 18:31 ` Rob Pike
2005-12-08 3:58 ` Lyndon Nerenberg
2005-12-08 4:10 ` Russ Cox
2005-12-08 4:55 ` Uriel
2005-12-07 3:56 ` Jeff Sickel
2005-12-06 15:57 ` jmk
2005-12-07 0:11 ` geoff
2005-12-07 0:17 ` Francisco J Ballesteros
2005-12-07 0:22 ` Steve Simon
2005-12-08 3:55 ` Lyndon Nerenberg
2005-12-06 12:46 ` erik quanstrom
2005-12-06 15:02 ` Brantley Coile
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=ee9e417a0512050407w7a2893d1of70d55dae332df87@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).