X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Mon, 23 Mar 2009 21:00:17 +0200
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: Documentation error
In-reply-to: <gq7rb5$glk$1@aioe.org>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <uhc1knjy6.fsf@gnu.org>
References: <ca683ba1-e029-4556-ae77-37e6cb3f5658 AT p6g2000pre DOT googlegroups DOT com> <gq7rb5$glk$1 AT aioe DOT org>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Rod Pemberton" <do_not_have AT nohavenot DOT cmm>
> Date: Mon, 23 Mar 2009 07:24:11 -0400
> 
> In libc.info under setdisk()'s "Return Value":
> 
>   "The highest drive actually present that the system can reference."
> 
> AFAICT, the DJGPP documentation doesn't say anything about a either a zero
> or a one based drive number being returned...

It does, in a way: look at the Example.

> Also, I think one could make a case for DJGPP that setdisk() should return
> the drive number that was set by setdisk(), or an error if the drive isn't
> present.

setdisk is a compatibility function, so it returns what its Turbo C
namesake does.