Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: From: "Jimen.Ching" To: cygwin AT sources DOT redhat DOT com Subject: fwrite inconsistency Date: Tue, 8 Aug 2000 12:18:46 -1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C00186.9F03378C" ------_=_NextPart_001_01C00186.9F03378C Content-Type: text/plain; charset="iso-8859-1" Hi all, The problem below produces "0 0" as output on HPUX and Solaris 2.5 with gcc 2.8.x. But using gcc 2.95.x on cygwin, I get "0 1". I also tried using Borland BCC, and I also got "0 1". Is GCC trying to behave like MS compilers under cygwin? Is it correct for size2 to contain 1? What does ANSI/ISO say about this? --jc ----------------------------------------------------- #include int main(int argc, char *argv[]) { int size1, size2; FILE *fp; fp = fopen("tst.log", "w"); size1 = fwrite(0, 1, 0, fp); size2 = fwrite(0, 0, 1, fp); printf("%d %d\n", size1, size2); return 0; } -- jimen AT adtech-inc DOT com Adtech, Inc. (808) 734-3300 ------_=_NextPart_001_01C00186.9F03378C--