| delorie.com/archives/browse.cgi | search |
| From: | Martin Str|mberg <ams AT ludd DOT luth DOT se> |
| Message-Id: | <200006121530.RAA29570@father.ludd.luth.se> |
| Subject: | Re: LONG: fat32 diff in cvs (second try) |
| In-Reply-To: | <Pine.SUN.3.91.1000612152842.5082A-100000@is> from Eli Zaretskii at "Jun 12, 2000 03:29:50 pm" |
| To: | djgpp-workers AT delorie DOT com |
| Date: | Mon, 12 Jun 2000 17:30:04 +0200 (MET DST) |
| X-Mailer: | ELM [version 2.4ME+ PL54 (25)] |
| MIME-Version: | 1.0 |
| 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 |
According to Eli Zaretskii:
> One more tidbit: the docs for FSEXT should be updated with the new
> FSEXT_llseek symbol.
Ok. But I have a question, in fsext.h there are:
typedef enum {
__FSEXT_nop,
__FSEXT_open,
__FSEXT_creat,
__FSEXT_read,
__FSEXT_write,
__FSEXT_ready,
__FSEXT_close,
__FSEXT_fcntl,
__FSEXT_ioctl,
__FSEXT_lseek,
__FSEXT_link,
__FSEXT_unlink,
__FSEXT_dup,
__FSEXT_dup2,
__FSEXT_fstat,
__FSEXT_stat,
__FSEXT_llseek
} __FSEXT_Fnumber;
But the texinfo document also mentions __FSEXT_ready_read,
__FSEXT_ready_write and __FSEXT_ready_error. Shouldn't these two
places match? I must be missing something.
Right,
MartinS
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |