Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: A New Forth Date: Sat, 08 Oct 2016 18:00:29 -0700 Organization: A noiseless patient Spider Lines: 26 Message-ID: <87fuo6uyj6.fsf@nightsong.com> References: <9dc136b0-5a06-4bad-b719-0e94358896f1@googlegroups.com> <1f740c55-e4d9-4e0f-993c-346e55ff7438@googlegroups.com> <87wphivdne.fsf@nightsong.com> <763508c2-cb4c-476f-96d1-95c603729e73@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="590ea01354cf4bcbcd857d7ebbd88128"; logging-data="20491"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19DkmiNTglfn4VgvYN3Jvsy" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:wPaxcop4ftRwuHK58cTBQmivPwM= sha1:1oyxmMwzvtRcYRviORImmoGc5Yk= Xref: csiph.com comp.lang.forth:51720 trans writes: > It's static as much as possible and dynamic otherwise, Normally I think of "dynamic" as meaning "runtime type tags". Maybe that's approximately what you plan to do with jump tables. > I want to create something that people can use on the high-end to > write modern end user applications -- a language that is very > approachable. But that still holds to Forth principles, so one could > still drop down to lower levels if they want/need to. You might look at Oforth, 8th, Factor, and Postscript as someone mentioned. I myself haven't yet understood the attraction of Forth-like syntax in those languages, at least for humans: once you're willing to have that many moving parts in an implementation, you might as well offer an automatic way to tell (e.g.) where the arg list for a function begins and ends. So you end up with something like Lisp instead of Forth. There's also Strongforth which may have already come up here. > On the surface Haskell seems great, but as I explored it more the > extreme focus on types, pure functionality and heavy academics, starts > to wear on code clarity, at least it seemed that way to me. Yes, it was invented as a research testbed rather than a software delivery mechanism. It's still a good way to get exposed to sophisticated type systems if you haven't seen them before.