Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: Could Forth be getting a bit of traction?
Date: Tue, 08 Sep 2015 21:00:55 -0700
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <87bndctf60.fsf@jester.gateway.pace.com>
References: <ca411208-dff1-45ff-8111-1dffbfb32baf@googlegroups.com> <998e315e-9945-4bbb-b512-4d5503746525@googlegroups.com> <c730b8d0-fc32-42b0-b05e-4d13d2a81036@googlegroups.com> <2eae1f37-03de-46cb-aec5-982f71867270@googlegroups.com> <e0288417-65a9-4d72-8d37-d2aeb8acbb01@googlegroups.com> <53e77c00-3c0d-449e-b8f2-9e274581d01b@googlegroups.com> <52bb77a4-a943-4d1b-a8a2-26a12d38f95a@googlegroups.com> <6a423e09-f98a-4891-9816-39b4ca33365b@googlegroups.com> <aee1940a-1660-4476-959a-0ebf68d21134@googlegroups.com> <da26bc07-688b-4107-821f-ec06254c2a8b@googlegroups.com> <62e1ded5-1982-4887-95e5-113c5f47eee1@googlegroups.com> <e63bf537-5a12-4a17-87b4-36f14639bebd@googlegroups.com> <a208c85f-e1eb-497f-9497-fe4b63e7ce78@googlegroups.com> <msndv8$7as$1@dont-email.me> <03bbb5ce-d533-46d5-ab0f-861e191deb3d@googlegroups.com> <5ceeed2c-264c-4849-adfb-3b9c8f7f15d3@googlegroups.com> <87fv2otihy.fsf@jester.gateway.pace.com> <89eec9fc-de84-4d04-bf53-84f3ed0e4bd3@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="4a8d07ad1a0f5884bbd8208f7dcd0e0f"; logging-data="32005"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/kV3XOo13uiWzkvb3WOSCY"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:VLRXSL5ipZ08F4pI/ZhK7FtxWXw= sha1:rMTTep1mVZY9fhVBb3Hk6d7um14=
Xref: csiph.com comp.lang.forth:41877

jim.brakefield@ieee.org writes:
> Programming in the large (e.g. using vectors and arrays as in Numpy)
> is both terse and avoids writing/testing a lot of loop code. 

Well there is FSL (Forth Scientific Library) though I haven't used it.

> One way to implement vector and array operators is to generate them
> dynamically, so it is useful to treat word lists as strings, put
> together the loop code and execute.  Of course this can be done by
> adding a tool vocabulary.

Not sure what you mean by tool vocabulary, but the above is certainly in
the range of existing Forth metaprogramming techniques.

> Another favorite is to have a precedence parser to convert an
> algebraic expression (starting from the character string
> representation) to a word definition (that uses locals?), and vice
> versa.

Things like this have been done but I don't remember specifics.