Xref: news2.mv.net comp.os.msdos.djgpp:5391
From: Thomas Demmer <demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De>
Newsgroups: comp.os.msdos.djgpp
Subject: FSE, some questions
Date: Wed, 26 Jun 1996 10:07:14 +0100
Organization: Lehrstuhl fuer Stroemungsmechanik
Lines: 43
Message-ID: <31D0FDC2.15FB@LSTM.Ruhr-UNI-Bochum.De>
NNTP-Posting-Host: bvb.lstm.ruhr-uni-bochum.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

First question:
In the info file for __FSEXT_alloc_fd():

"The module is responsible for calling _close() on
the descriptor after setting the handler function to 
zero in the extended close handler"

What I tried was
[...]
  case __FSEXT_close :{
     int fd = va_arg(args, int);
     // Shutdown COM-Handler....
     [...]
     _close(fd);
     return EMULATED;
[...]
This caused _close to trigger my handler again, obviously
not what I intended. 

Second Question:
Can fcntl() be extended to communicate with a File
System Extension handler? I'm thinking of something
like
 fd=open("/dev/ttyS0",O_NOBLOCK| O_RDWR);
 fcntl(fd,F_SETCOM, S9600 | B8 |P_NONE |XON_XOFF);  


-- 
Ciao
Tom



*************************************************************
* Thomas Demmer                                             *
* Lehrstuhl fuer Stroemungsmechanik                         *
* Ruhr-Uni-Bochum                                           *
* Universitaetsstr. 150                                     *
* D-44780  Bochum                                           *
* Tel: +49 234 700 6434                                     *
* Fax: +49 234 709 4162                                     *
* http://www.lstm.ruhr-uni-bochum.de/~demmer                *
*************************************************************