| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | FTS-0501 |
18 Feb 96 08:36, Paul Edwards wrote to Bob Lawrence: > When was the last time you checked the return code from fclose()? You > do realise that if fclose() fails (on writing) you could actually lose > data? Regarding fclose the C standard says, "The fclose function returns zero if the stream was successfully closed, or EOF if any errors were detected." If fclose returns EOF, is the file closed or still open? If errors are detected the file may well be closed by fclose regardless. The standard is ambiguous here. > The best argument against this "committee never works" theory is the > ANSI C standard. It's faultless. BFN. Paul. Ummm. --- Msgedsq/2 3.30* Origin: This one HAS to be original X (3:635/727.4{at}fidonet) SEEN-BY: 50/99 78/0 635/309 503 544 727 640/230 690/718 711/401 410 413 430 SEEN-BY: 711/808 809 934 712/610 713/888 800/1 7877/2809 @PATH: 635/727 544 50/99 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.