Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail From: Daniel Cerqueira Newsgroups: comp.lang.forth Subject: Re: Back to the Forth Virus Date: Mon, 08 Jun 2026 13:56:25 +0100 Organization: A noiseless patient Spider Lines: 58 Message-ID: <87bjdl2nt2.fsf@lispclub.com> References: <11069n1$3617t$1@dont-email.me> <1106c8c$37c1i$1@dont-email.me> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Injection-Date: Mon, 08 Jun 2026 13:02:11 +0000 (UTC) Injection-Info: dont-email.me; logging-data="3397445"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX194OB6z10jDkgwqxLTtDpWKCMY+tylPj3E="; posting-host="c30ddb5bc527ee888136ba7a02b2f4f6" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:62oCygqITRrveVTAmkPIX566SAw= sha1:dXmyrhoL38ziKp4vLKb7DlN72c8= sha256:zEZq9rlOh1WAno8lrvu7mTSGR5wGD2g+SLZqZvybnV0= sha1:WVIKp7j8ccp4ui+hsFtRwTczQi0= OpenPGP: id=0x964FC110C40AD575; url="https://openpgpkey.lispclub.com/.well-known/openpgpkey/lispclub.com/hu/wwhaoe1fy5idwyj4xx847eqerems5rwb?l=dan.list"; preference=signencrypt Content-Language: en Xref: csiph.com comp.lang.forth:135151 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Ruvim writes: > On 2026-06-08 11:40, clv2020 wrote: >> some years passed and now I would be interested to try Forth again. >> First question: Which Forth is used nowadays for PCs under >> Windows11? I tried Win32Forth, ciForth and the old volksForth in an >> Oracle VirtualBox. (gForth, bigForth, VFX, Swiftforth are too big >> for me for the moment). What would you recommend? [...] > A reliable way is to build the executable file by yourself. > > Gforth can be build and used under WSL on Windows from a tarball; see > the instruction at: > > > Aside from a number of dependencies and the lengthy build process, > Gforth is quite user-friendly. Just to inform, that I was unsuccessful with building GForth on a GNU operating system. Besides the build error, the public PGP key they used to sign the tarball is nowhere to be found. So I had to blind-trust, then got a build error. If a build error also happens in windows, I wouldn't be surprised. Cheers for Freedom, =2D-=20 A little Consideration, a little Thought for Others, makes all the difference. ~ Alan Alexander Milne --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJmBAEBCgBQFiEEOVeKaEm0xBhCsMmYlk/BEMQK1XUFAmomu/kbFIAAAAAABAAO bWFudTIsMi41KzEuMTEsMiwyFhxkYW4ubGlzdEBsaXNwY2x1Yi5jb20ACgkQlk/B EMQK1XWeGA//XVnEH0ACcusOYZ9Or24rQ5l+8vDMECrmsz5d2BwpthWmBcVldAn1 m4f4+vnrDT23bdA3wAG1nJeB028SbxEiUARQegKw9EOwW64PTgzDNy6iDAC+LFZV W010kmvh1HcNQnuycQnd6o5qcvoY/aISxNpbf8GkoQzpe3bGu95//9PqqxRSaIg2 bbzaY1vacJx0yo+gfANGK0HzgH2XTMMJLtnq3BmJXa3pHB+51UXKRdrXleNRwu6K 6f7SInwvyWABXdYVV+zjt+TVgHhf74g+KFJkeLbfowQV4SvcmHBnWGcJuR9w2zQc ccCBt+NMnU0seggEP59vNxVhdZcy/GWzyzjey75zGuHZbeyiHpCZlp5Kzpst4zPo ioTsmzJGrkaiGdKnp3wkqGAnELYyEp6ZQB7+lgS81hauLwMhaPcHI8MTK2+PrJeC qmc2sLY/ECgNGlR/OlJmVEjKAMJl9VIa149AUADTXIeYqAfIgxA7O7Vxt98OqxUQ ot9EuKKcg2NXw3L0AOoE3B+9Q89TCmcih3R7Tlc2DC7OYVTGqaoVB4kSJCL55zjG dEkCQBbSE0p0wpboNLASiMkx8Kz35b2cfRYJXpqB3ZaAPFiAqUf6txDA63XkPm8o CY6bomvXwdzIk+PXHM4EkGB9lA8W1vp6I4idPA8xcCaNYpah7fI20so= =2qW3 -----END PGP SIGNATURE----- --=-=-=--