Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!purdue!bouma From: bouma@cs.purdue.EDU (William J. Bouma) Newsgroups: comp.lang.forth Subject: Re: Believe or not, Forth in CS! Message-ID: <13984@medusa.cs.purdue.edu> Date: 21 Mar 91 21:47:56 GMT Article-I.D.: medusa.13984 References: <9103210411.AA14444@ucbvax.Berkeley.EDU> Sender: news@cs.purdue.EDU Organization: Department of Computer Science, Purdue University Lines: 24 In article <9103210411.AA14444@ucbvax.Berkeley.EDU> UNBCIC%BRFAPESP.BITNET@SCFVM.GSFC.NASA.GOV writes: >Sorry, but you have to build a very concrete base anyway in any language. The >difference is that in non-extensible languages the program is difficult all th Oooh, I hate that when you say your sorry! >It's very simple: if you can only merge tools, you don't have nothing -- if al >the correct tools were available, we wouldn't program anymore. If it is so simple, why didn't I understand a single thing you just said? >We think this way: you will always have to abstract data types, so it's better >provide a way to build *THE* data type I need than to provide many types and n That is just it. I would like to see Forth provide a way to do that. >that they are useful when they are useful, and, until them, we are not going t >put them in our systems. When we want them, we use them! Why can't you see >this?! Take a look at HS/Forth... What you want that it do not provide? Don't I do not mean this as an insult. It is just from the way you talk I cannot imagine you have written much code. -- Bill