Related articles |
---|
Different Strokes for Different Folks (Was: Assessing a language) eifrig@beanworld.cs.jhu.edu (1993-01-06) |
Re: Different Strokes for Different Folks (Was: Assessing a language) purtilo@cs.umd.edu (1993-01-07) |
Re: Different Strokes for Different Folks (Was: Assessing a language) dyer@airplane.sharebase.com (1993-01-07) |
Re: Different Strokes for Different Folks (Was: Assessing a language) andrewb@cs.washington.edu (1993-01-09) |
Re: Different Strokes for Different Folks (Was: Assessing a language) axs@cs.bham.ac.uk (1993-01-13) |
Re: Different Strokes for Different Folks (Was: Assessing a language) ludemann@quintus.com (Peter Ludemann) (1993-01-22) |
Re: Different Strokes for Different Folks (Was: Assessing a language) Alain.Callebaut@cs.kuleuven.ac.be (1993-01-25) |
Re: Different Strokes for Different Folks (Was: Assessing a language) gym@dcs.ed.ac.uk (Graham Matthews) (1993-01-25) |
Newsgroups: | comp.ai,comp.compilers |
From: | andrewb@cs.washington.edu (Andrew Berg) |
Organization: | Comp. Sci. & Eng. Dept., Univ. of Washington, Seattle |
Date: | Sat, 9 Jan 1993 17:42:30 GMT |
References: | 93-01-036 |
Keywords: | design, forth |
> Surprisingly, there hasn't been much work in developing
> heterogenous programming environments, to support a sort of "mix and
> match" approach to programming. Such tools would go a long way to
> alleviating the language holy wars, I think.
It seems to me that this is (somewhat) FORTH does, in that if you
want a word to do something, you can.
I am not much of a FORTH programmer--or advocate--but I've seen
Smalltalk-like FORTH environments, and I've written LISP-y environments.
And I see no reason why one couldn't implement PROLOG-y words, or ML.
The real weakness with FORTH is exactly the opposite of the other
do-everything languages: there is no standard library of stuff to draw on.
Anyone who wants an array must create his own kind of array. This is true
for most every other normally standard language feature. If many shops
have disagreements about how to indent 'C' code, how will they agree on
how to implement something complicated?
andrewb@cs.washington.edu
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.