Date: Sun, 10 Jan 1999 13:43:44 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc: DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject: Re: rand48 for libc
In-Reply-To: <199901091259.NAA01314@sister.ludd.luth.se>
Message-ID: <Pine.SUN.3.91.990110134301.20678b-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com


On Sat, 9 Jan 1999, Martin Str|mberg wrote:

> Here's the patch to add *rand48() functions to libc. This time with
> documentation. 

Thanks.  Some comments:

> +@code{srand48()} or @code{seed48()}. A call to @code{lcong48()}
> +changes a and c (and the internal state).

You should not include the parens () when referring to functions.  The
parens are redundant at best (since the @code markup already makes the
name of the function stand out), and might be confusing, since people
might think these functions don't accept arguments.

Simply say @code{srand48}, @code{seed48}, etc.

> +@code{srand48()} sets the high order 32 bits to the argument
> +@code{seed}.

Formal arguments should be typeset with @var{}, not with @code{}:

  @code{srand48} sets the high order 32 bits to the argument @var{seed}.

There are several other cases like this.