Re: [stack] Re: Joy noob checking in!
Duke Normandin <[email protected]> Mon, 10 May 2010 15:06:31 -0600 (MDT)
| Newsgroups | gmane.comp.lang.concatenative |
|---|---|
| Message-ID | <alpine.OSX.2.01.1005101457500.20753@q75-154-107-232.noufvn.gryhf.arg> |
On Mon, 10 May 2010, William Tanksley, Jr wrote: [snip] > > I must admit that Joy _did_ appeal to me the first time I saw it. How > > well I could do with it may never be known. What do you think of > > Factor? > > I like it a lot -- it's a clever language, probably the most complete > application-oriented concatenative language (certainly the most > complete outside of the proprietary Forth vendors). I usually > recommend trying it first; Joy is a fun language, but is rather > academically oriented and not really actively maintained. I guess I'll be Factoring out Joy as of right now! ;) > >> By the way, if you HAD been interested in bare metal, I'd have > >> suggested learning colorForth and reimplementing it from scratch. Heh. > > Why re-implement from scratch? > > Because it's the only way to really understand the bare metal -- and > the only way to get a language ideal for manipulating YOUR machine. I see! Re-implementing it in C? or Assembly Language? > > and why colorForth? > > Because it's the simplest dialect of Forth, based on years of Chuck > Moore's experience and centered around the idea of bare metal. (It has > to be said, though, that Chuck's idea of working with bare metal > involved writing Color Forth for the Pentium, writing a chip designer > program on it, designing a whole new chip, rewriting for that chip, > and designing the successor to that chip on the newly fabbed chip > itself. I'm not up to that, and I doubt anyone aside from Chuck is.) Simple is Good! Simplest is even better! ;) I wonder why there's no mention of it on c.l.f.? I know that Fox and Passinitti (sp?) don't hit it off. > There's a good implementation with examples here: > http://rainbowforth.sourceforge.net/; its own full source code is at > http://rainbowforth.sourceforge.net/blocks.html and might be worth a > quick skim. Chuck's code is public domain as well, but... Well, it's > like expecting to read Knuth in one sitting. I'll have a look. -- Duke A: Backwards from the way folks normally read text A: Because it forces conversations to flow in a nonsensical order. Q: Why is top-posting a major PAIN? [http://en.wikipedia.org/wiki/Netiquette]