From: <ams AT ludd DOT luth DOT se>
Message-Id: <200304221830.h3MIUvxW008929@speedy.ludd.luth.se>
Subject: Re: @var, -, @code?
In-Reply-To: <3EA52D96.14D87106@yahoo.com> "from CBFalconer at Apr 22, 2003 07:55:02
 am"
To: djgpp-workers AT delorie DOT com
Date: Tue, 22 Apr 2003 20:30:57 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL78 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-MailScanner: Found to be clean
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

According to CBFalconer:
> 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).

Ok. I'll go with this one.

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

Go ahead, your welcome.


Right,

						MartinS