Newsgroups: | comp.compilers,alt.folklore.computers,comp.lang.forth |
From: | Peter da Silva <peter@Starbase.NeoSoft.COM> |
Keywords: | forth, history |
Organization: | NeoSoft Internet Services +1 713 684 5969 |
References: | 94-09-076 94-09-097 |
X-Provider: | NeoSoft, Inc.: Internet Service Provider (713) 684-5969 |
Date: | Tue, 20 Sep 1994 12:04:33 GMT |
[my RatForth language description]
>[Gee, sounds not altogether like bc, the C-ish front end to the RPN dc. -John]
Don't you mean unlike (grin)? [sure, we Old Farts can't type -John]
Until this moment the similarity to bc/dc didn't occur to me. It's obvious
now I think of it.
The implementation, though, was in Forth. The word "define" was a Forth word
that compiled ratforth into a buffer until it ran out of matching braces, so
you could mix ratforth with forth interchangably:
: this blah blah blah ;
define that { blah blah; blah; }
I generally used Ratforth for complex expressions, and you could take
obscene advantage of the implementation. For an example:
define peek { @(2+dup()) }
Becomes:
: peek dup 2 + @ ;
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.