home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sdd.hp.com!uakari.primate.wisc.edu!ames!agate!dog.ee.lbl.gov!hellgate.utah.edu!lanl!cochiti.lanl.gov!jlg
- From: jlg@cochiti.lanl.gov (Jim Giles)
- Newsgroups: comp.lang.fortran
- Subject: Re: Small Language Wanted
- Message-ID: <1992Aug28.153844.2934@newshost.lanl.gov>
- Date: 28 Aug 92 15:38:44 GMT
- References: <H.3lvmyc56w&A@lionbbs.bs.open.de> <17gsgnINN903@network.ucsd.edu> <9224014.17999@mulga.cs.mu.OZ.AU> <1992Aug27.151505.19860@hubcap.clemson.edu> <9224102.1936@mulga.cs.mu.OZ.AU> <1992Aug28.102630.1@vxdesy.desy.de>
- Sender: news@newshost.lanl.gov
- Organization: Los Alamos National Laboratory
- Lines: 19
-
- In article <1992Aug28.102630.1@vxdesy.desy.de>, pawlak@vxdesy.desy.de writes:
- |> [...]
- |> Pardon me, but does C have any I/O? It seems to me that all it has are
- |> functions with side-effects... Having things that 'can be implemented'
- |> instead built-in features leads to: 1) having them implemented by various
- |> people in incompatible ways, 2) making the programs larger, and thus harder
- |> to read, as any program using such thing has to declare it first.
-
- C's I/O is every bit as standardized as Fortran's in that the functions
- which are referred to here are defined as part of the language's required
- library support. Since Fortran I/O is also *usually* supported by compiler
- generated library calls, and since ANSI C allows compliant compilers
- to special case standard functions anyway (by inlining them, etc. - provided
- it has reliably determined that no user replacements have been made),
- this makes C's I/O as built-in as Fortran's. Which is actually a better
- design depends on what you're trying to do.
-
- --
- J. Giles
-
