Message-ID:	<3EA52D96.14D87106@yahoo.com>
Date:	Tue, 22 Apr 2003 07:55:02 -0400
From:	CBFalconer <cbfalconer AT yahoo DOT com>
Organization:	Ched Research
X-Mailer:	Mozilla 4.75 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: @var, -, @code?
References:	<200304210840 DOT KAA05189 AT lws256 DOT lu DOT erisoft DOT se> <3995-Tue22Apr2003095706+0300-eliz AT elta DOT co DOT il>
Reply-To:	djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> > From: Martin Stromberg <Martin DOT Stromberg AT epl DOT ericsson DOT se>
> > Date: Mon, 21 Apr 2003 10:40:38 +0200 (MET DST)
> > >
> > > Rephrase again is my recommendation:
> > >
> > >   If @var{endp} is not a null pointer, it will be set to point
> > >   to the first unconverted ...
> >
> > But that says (C-code): "endp = <something>;" not "*endp =
> > <something>;".
> 
> Then how about the following?
> 
>   The pointer to the first unconverted character will be stored in
>   the object pointed to by @var{endp}, if @var{endp} is not a null
>   pointer.

That has a different emphasis.  IMO the first thing the user wants
to know is what to pass in that parameter.  The second is what it
does.  Thus possibly:

   If @var{endp} is not a null pointer, a pointer to the first
   unconverted character will be stored in the location pointed 
   to by @var(endp).  Thus endp is normally the address of a
   pointer to a char (or NULL).

Don't know why I am sticking my nose in here.  :-)

-- 
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
   Available for consulting/temporary embedded and systems.
   <http://cbfalconer.home.att.net>  USE worldnet address!

- Raw text -