Date: Mon, 8 Sep 1997 18:00:28 -0400 (EDT)
Message-Id: <199709082200.SAA26057@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: molnarl AT cdata DOT tvnet DOT hu
CC: djgpp-workers AT delorie DOT com
In-reply-to: <34141607.22FD892B@cdata.tvnet.hu> (message from Molnar Laszlo on
	Mon, 08 Sep 1997 17:13:11 +0200)
Subject: Re: fsext question
Precedence: bulk


> I've just finished a fsext for perl, which seems to work. It virtualizes
> the glob() function, so now "/dev/dosglob/searchpattern" opens a "file"
> which contains the matched filenames. And here is my question: as I saw
> lseek() and fstat() don't use fsext, so strange things could happen when
> an application tries to find the size of this virtual file. Is it a real
> problem?

There are lots of I/O functions that don't support FSEXT yet.  I'm not
sure what to do with them.  FSEXT was originally added to support
virtual character and stream devices, not files, so that's where the
effort went.