Related articles |
---|
Re: lcc intel backend? compile time? rds95@csc.albany.edu (1993-10-13) |
Re: lcc intel backend? compile time? graham@pact.srf.ac.uk (1993-10-13) |
Re: lcc intel backend? compile time? cliffc@rice.edu (1993-10-13) |
Re: lcc intel backend? compile time? rds95@csc.albany.edu (1993-10-13) |
Re: lcc intel backend? compile time? pardo@cs.washington.edu (1993-10-20) |
Re: lcc intel backend? compile time? henry@zoo.toronto.edu (1993-10-20) |
Re: lcc intel backend? compile time? tchannon@black.demon.co.uk (1993-10-21) |
Re: lcc intel backend? compile time? henry@zoo.toronto.edu (1993-10-22) |
Newsgroups: | comp.compilers |
From: | henry@zoo.toronto.edu (Henry Spencer) |
Keywords: | C, interpreter |
Organization: | U of Toronto Zoology |
References: | 93-10-094 |
Date: | Fri, 22 Oct 1993 20:02:28 GMT |
tchannon@black.demon.co.uk writes:
>There seems to be a low takeup of interpreted C which given the lower
>reliability of freshly coded source implies that a fast crash cycle isn't
>that important or is there anouther explanation?
There is another explanation, a very simple one: the existing C
interpreters are expensive add-ons that shortsighted managers often see as
unnecessary frills. If there were a good one available free, you'd see a
whole lot more use of interpreted C. As it is, the use is not
insignificant despite the costs, since at least one company is making a
living selling a C interpreter.
--
Henry Spencer @ U of Toronto Zoology, henry@zoo.toronto.edu utzoo!henry
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.