Re: Do all programming languages use files?

Scott Moore wrote:
>
> Duane Bozarth wrote:
> > Scott Moore wrote:
> > ...
> >
> >>I'm not trying to beat you up here. I am trying to make you realize that language
> >>designers don't consider libraries to be part of the language itself. The library
> >>is a support system, like a linker or loader. The language itself has several
> >>properties that are distinct from libraries:
> >
> > ...
> >
> > As you mentioned earlier, it's semantics.
> >
> > The original designers didn't, the current ISO Standard does consider
> > the libraries as part of the Standard Definition.
>
> Of what? If you look at the specification, it is clearly marked as "the standard
> library", not "part of the language", and in fact is in a completely separate
> section away from the language part.

I consider the Standard as including both as a definition of "the
language".

That the library is implemented in a core is the semantics argument.

But, I understand your point that the library wasn't considered
fundamental originally, at least.
.

Relevant Pages

  • Re: read and write
    ... the C standard says otherwise. ... which are also not a part of the language. ... of these libraries are part of "C", whatever it is, since they contain ... However, any hosted implementation is required to include the entire standard C library, and prior to the standard the first edition of K&R says "Chapter 7 describes the standard C I/O library, which provides a common interface to the operating system. ...
    (comp.lang.c)
  • Re: read and write
    ... the C standard says otherwise. ... which are also not a part of the language. ... of these libraries are part of "C", whatever it is, since they contain ... common interface to the operating system. ...
    (comp.lang.c)
  • Re: [LONG] Re: Why code completion and early error checking are needed
    ... >> the programmer who wants such features. ... > libraries to find the type declaration. ... If you type std::vector that means the one from the Standard. ... > of the language to have certain naming and declaration standards ...
    (comp.lang.cpp)
  • Re: Qi Seems Great
    ... Common Lisp will simply trounce anything else in the long ... but having third party libraries to support the new ... ideas come along doesn't mean that the language itself will grow. ... Having in mind that the CL standard is rather old, ...
    (comp.lang.lisp)
  • Re: Forth and Unix -- history
    ... but modern Forths mostly drive them away. ... You have no justification to call STOIC retro nostalgia given that Standard Forth is pretty much stuck in the mid 70's. ... Users provide a large fraction of those libraries for C. Publicly. ... users must find the language comfortable in order to create such things. ...
    (comp.lang.forth)