Re: Do all programming languages use files?

Scott Moore wrote
(in article <devok8$5ov$3@xxxxxxxxxxxxxxxxxxxxxx>):

> Richard Heathfield wrote:
>> Scott Moore said:
>>
>>
>>> Ben Pfaff wrote:
>>>
>>>> Scott Moore <samiam@xxxxxxxxxxxx> writes:
>>>>
>>>>
>>>>> C doesn't have files.
>>>>
>>>> Hosted implementations of standard C implement a set of functions
>>>> for file I/O.
>>>
>>> Again, C does *NOT* have file I/O. Think carefully about the question.
>>
>>
>> As far as ISO is concerned, the standard C library is part of the language,
>> except for freestanding implementations (which are not required to support
>> the entire library).
>>
>
> Semantics.

Yes, and as all serious programmers know, semantics are
important, rather than being a word to insert in place of 'I
don't want to argue about this'.

> If its a library, then you could well argue that GPS is built
> into the language, since there are undoubtedly libraries for that.

No, you could not argue that. You seem to be deliberately
ignoring the word 'standard' immediately before 'C library'
above. Apart from people doing embedded work, almost everybody
with a C compiler has access to the standard C library the
second they install the compiler package. Can you name a C
compiler that comes with a GPS library built-in? More
importantly, does the ISO C standard specify a <stdgps.h> header
file to define its interfaces?



--
Randy Howard (2reply remove FOOBAR)

.

Relevant Pages

  • Re: C89, size_t, and long
    ... libraries which have useful stuff). ... So because others here can't think of a good reason to use long instead of size_t and you can't prove there is never such a reason, we must all assume there could be a good reason to not use the mechanisms provided by the standard to deal with a problem? ... If you are claiming there is a reason to avoid the mechanisms the standard provides to allow portability then it is up to *you* to prove your point, not up to others to disprove it. ... but you can hardly blame the consequences on the Standard headers. ...
    (comp.lang.c)
  • Re: C89, size_t, and long
    ... libraries which have useful stuff). ... So because others here can't think of a good reason to use long instead of size_t and you can't prove there is never such a reason, we must all assume there could be a good reason to not use the mechanisms provided by the standard to deal with a problem? ... want to have standard headers included in their own headers which ...
    (comp.lang.c)
  • Re: comparing doubles for equality
    ... AFAIK there is no ANSI/ISO standard for it. ... Fortran 95 seem to have some built-in operators but it's not clear ... LIA,GIA,ICE libraries for interval methods in C++ from Delisoft ... Actually I've been for quite some months proposing getting together ...
    (comp.programming)
  • Re: "Criticism of the C programming language ??????"
    ... "that's not in the standard, ... rewrites of the compiler. ... PH> They got all the compiler vendors to agree to a common ... or graphics libraries or threading libraries, ...
    (comp.lang.c)
  • Re: OT: Requesting C advice
    ... fit in the standard process memory footprint of a VAX at the time. ... in the libraries--and indeed how many libraries there were going to be. ... had (a PDP-11 and a VAX), the linker couldn't handle the library size. ... a nice Morrow Microdecision with two floppy disk drives. ...
    (Fedora)