Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <02ff01c0b916$66480970$0200a8c0@lifelesswks> From: "Robert Collins" To: Subject: clearerr Date: Fri, 30 Mar 2001 21:33:49 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 30 Mar 2001 12:33:43.0231 (UTC) FILETIME=[A81D2CF0:01C0B915] I'm confused - newlib's clearerr calls __sclearerr, but I can't find that anywhere. cygwin.dindefines clearerr and _clearerr, but I can't find them in the source.. In testing the fifo semantics, I've found that the expected behaviour for a fifo on freeBSD is that clearerr() should re-open the fifo, allowing further writes to take take place.. i.e. a reader can loop clearerr() read to eof and the pipe can have multiple separate writers write to the pipe and exit. Without clearerr or a rewind(), the pipe gets marked eof and stays eof. most OS's seem to simply use rewind() to the same effect, so I'm implementing that. The question I have is: will clearerr() actually call any cygwin code? Rob