From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0512050407w7a2893d1of70d55dae332df87@mail.gmail.com>
Date: Mon,  5 Dec 2005 07:07:25 -0500
From: Russ Cox <rsc@swtch.com>
To: 9fans <9fans@cse.psu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: [9fans] irc answers - man and memmove
Topicbox-Message-UUID: b80ea16e-ead0-11e9-9d60-3106f5b1d025

(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