Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Programming > Forth > Re: part 21 ass...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 26 of 54 Topic 3806 of 4284
Post > Topic >>

Re: part 21 asserts forth best for small memory systems, would lisp be better in non small mem?

by Marc Olschok <nobody@[EMAIL PROTECTED] > Mar 11, 2008 at 07:21 PM

John Doty <jpd@[EMAIL PROTECTED]
> wrote:
> Elizabeth D Rather wrote:
> > John Doty wrote:
> > ....
> >> Please leave the argument in place. To snip here is evasion.
> > 
> > Ok.
> > 
> >> My argument is:
> >>
> >> 1. There is little published shareable Forth code, relative to other 
> >> languages. This seems beyond dispute.
> >>
> >> 2. You and others asserted that this is not because Forth code is not

> >> shareable, but because shareable code is proprietary, and that there 
> >> is plenty of such code.
> >>
> >> This requires that somehow Forth, unlike other programming languages,

> >> produces shareable code only if code is not to be published. If this 
> >> is true, it indicates weaknesses in Forth. Weaknesses, if correctly 
> >> identified, may often be repaired.
> >>
> >>>
> >>> There!  Right there, you repeat your basic logical error.  You have 
> >>> not established any "this requires that..." or "an unavoidable 
> >>> consequence" link.
> >>
> >> There, right there, you repeat your basic evasion. How is it that 
> >> Forth can only produce proprietary code?
> > 
> > Forth can certainly produce sharable, publishable code.  There is 
> > nothing whatever intrinsic to Forth that precludes sharable code.  The

> > reason there isn't a lot of published code has nothing to do with
Forth 
> > but a lot to do with the cultures in which it is most widely used.
> 
> You just contradicted yourself, and took a step toward a possible 
> reason. If Forth was acceptable to to the cultures that produce 
> publishable code (as it once was!) there would be no issue. So, we 
> merely restate the problem: what drove those cultures that produce 
> publishable code away from Forth?
> 
> Don't try the "fa****on" baloney. The world's experts in astronomical 
> instrumentation don't give a hoot about fa****on: they care about what 
> gets the job done. That's why they once embraced unfa****onable Forth, 
> and I believe also why they dropped it as the alternatives matured and 
> Forth remained frozen in an immature state.

What did the world's experts in astronomical instrumentation publish
during the time they used Forth? I do not doubt that they did publish
but I am curious whether their publications actually included
anything about the software used (let alone published code).
I know only of Julian article in a journal on computational physics
(I do not know the exact reference right now), but he was probably
not in the groups of astronomers you meant.

You may also want to reconsider the following questions:

(a) what particular weakness of the Icelandic language prevents its
use in comp.lang.forth?

(b) what made european scientists abandon Latin as common language?

(c) what drove scientists away from German towards English as a language
to publish in?

(d) what particular property of the number 2 is responsible for it
being a zero of the polynomial  X^2 - 4X + 4  ?

In each of the above, you will find that concentrating on an explanation
in terms only of the particular individual object does not go far in
answering the question.

Marc
 




 54 Posts in Topic:
Re: part 21 asserts forth best for small memory systems, would l
m-coughlin <m-coughlin  2008-03-07 10:38:11 
Re: part 21 asserts forth best for small memory systems, would l
Elizabeth D Rather <er  2008-03-07 08:06:59 
Re: part 21 asserts forth best for small memory systems, would l
Richard Owlett <rowlet  2008-03-07 12:50:19 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-07 12:14:26 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-08 01:30:31 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-07 18:53:16 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-08 02:41:56 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-08 16:03:35 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-09 16:12:17 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-09 10:51:39 
Re: part 21 asserts forth best for small memory systems, would l
Elizabeth D Rather <er  2008-03-09 08:33:40 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-09 13:37:07 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-10 15:43:19 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-10 10:10:29 
Re: part 21 asserts forth best for small memory systems, would l
Bernd Paysan <bernd.pa  2008-03-10 17:50:30 
Re: part 21 asserts forth best for small memory systems, would l
Elizabeth D Rather <er  2008-03-10 08:13:12 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-10 13:04:55 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-10 20:24:04 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-10 14:36:11 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-10 20:52:30 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-10 15:06:33 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-10 22:25:21 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-10 16:56:41 
Re: part 21 asserts forth best for small memory systems, would l
"Stan Katz" <  2008-03-12 18:00:10 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-12 16:13:31 
Re: part 21 asserts forth best for small memory systems, would l
Marc Olschok <nobody@[  2008-03-11 19:21:16 
Re: part 21 asserts forth best for small memory systems, would l
Aleksej Saushev <asau@  2008-03-11 23:05:58 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-11 22:42:04 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-10 20:19:34 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-10 19:52:18 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-10 14:11:26 
Re: part 21 asserts forth best for small memory systems, would l
Aleksej Saushev <asau@  2008-03-10 23:21:00 
Re: part 21 asserts forth best for small memory systems, would l
Andrew Haley <andrew29  2008-03-10 21:24:12 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-10 16:02:05 
Re: part 21 asserts forth best for small memory systems, would l
Andrew Haley <andrew29  2008-03-11 10:34:01 
A Brief Look at History (Re: part 21 asserts forth best for smal
m-coughlin <m-coughlin  2008-03-11 22:09:03 
Re: part 21 asserts forth best for small memory systems, would l
Duke Normandin <dukeof  2008-03-11 15:04:25 
Re: part 21 asserts forth best for small memory systems, would l
Bernd Paysan <bernd.pa  2008-03-11 16:40:14 
Writing Many New Versions of Forth (was Re: part 21 . . . )
m-coughlin <m-coughlin  2008-03-14 17:08:11 
Re: part 21 asserts forth best for small memory systems, would l
Duke Normandin <dukeof  2008-03-11 17:14:42 
Re: part 21 asserts forth best for small memory systems, would l
Elizabeth D Rather <er  2008-03-11 21:59:19 
Re: part 21 asserts forth best for small memory systems, would l
Aleksej Saushev <asau@  2008-03-13 00:43:39 
Re: part 21 asserts forth best for small memory systems, would l
Bernd Paysan <bernd.pa  2008-03-13 16:12:17 
Re: part 21 asserts forth best for small memory systems, would l
Aleksej Saushev <asau@  2008-03-15 00:00:58 
Re: part 21 asserts forth best for small memory systems, would l
Marc Olschok <nobody@[  2008-03-14 21:32:04 
Re: part 21 asserts forth best for small memory systems, would l
Duke Normandin <dukeof  2008-03-11 20:44:40 
Re: part 21 asserts forth best for small memory systems, would l
Elizabeth D Rather <er  2008-03-11 21:46:47 
Re: part 21 asserts forth best for small memory systems, would l
Duke Normandin <dukeof  2008-03-10 05:19:15 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-07 11:56:33 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-08 00:16:03 
Re: part 21 asserts forth best for small memory systems, would l
John Doty <jpd@[EMAIL   2008-03-07 17:34:02 
Re: part 21 asserts forth best for small memory systems, would l
Albert van der Horst <  2008-03-08 10:58:33 
Re: part 21 asserts forth best for small memory systems, would l
Guy Macon <http://www.  2008-03-08 17:11:27 
Re: part 21 asserts forth best for small memory systems, would l
kenney@[EMAIL PROTECTED]   2008-03-08 04:20:28 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Sat Oct 11 18:38:11 CDT 2008.