Date: Tue, 13 Jun 2000 13:11:54 +0300 (IDT)
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 AT delorie DOT com
Subject: Re: LONG: fat32 diff in cvs (second try)
In-Reply-To: <200006121530.RAA29570@father.ludd.luth.se>
Message-ID: <Pine.SUN.3.91.1000613131134.16888E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Mon, 12 Jun 2000, Martin Str|mberg wrote:

> But the texinfo document also mentions __FSEXT_ready_read,
> __FSEXT_ready_write and __FSEXT_ready_error. Shouldn't these two
> places match?

__FSEXT_ready_* are bits returned by the extension that hooks
__FSEXT_ready type of requests (such an extension emulates the
`select' function).  They are not types of extensions.  So they
shouldn't be in the enum.