Xref: utzoo comp.lang.c:8809 comp.unix.questions:6374 comp.os.vms:5525
Path: utzoo!mnetor!uunet!lll-winken!lll-tis!mordor!sri-spam!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.lang.c,comp.unix.questions,comp.os.vms
Subject: how to avoid fflush after fclose?
Message-ID: <21774@teknowledge-vaxc.ARPA>
Date: 1 Apr 88 06:09:59 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 13

Calling fflush after fclose appears not to hurt under Unix, but VMS returns
EOF.  Is there a way to test if a FILE *fptr has been closed so that I don't
inadvertently call fflush after fclose?  Ideally the solution is a function
in both the usual Unix C libraries and in the VMS C runtime library.

(If you're reading this in comp.os.vms, please reply by email, as I don't
usually pay any attention to VMS :))

Thanks,
Mike Khaw
-- 
internet:  mkhaw@teknowledge-vaxc.arpa
usenet:	   {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail:	   Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303