The Forth programming language (forth) group
-
Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 12-Apr-2018 13:08:31 UTC Hallå Kitteh @ralph
http://factorcode.org/ !forth -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Friday, 02-Feb-2018 01:10:18 UTC Hallå Kitteh !forth -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Monday, 18-Dec-2017 01:41:55 UTC Hallå Kitteh > DX-Forth v4.30 - Forth compiler for MS-DOS (2017-02-11)
> For all IBM-PC compatible machines with
MS-DOS 2.x or better.
This is an impressive level of dedication.
http://dxforth.netbay.com.au/
!forth -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 14-Nov-2017 07:51:32 UTC Hallå Kitteh @h The !forth group has gained followers, we're 7 now! -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Monday, 06-Nov-2017 03:11:41 UTC Hallå Kitteh @jk !forth -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 22-Aug-2017 07:40:59 UTC Hallå Kitteh http://wiki.forth-ev.de/doku.php/en:projects:gforth-android:start
Not sure where to find the Android-specific source. No package on f-droid.
Still, probably something interesting to try out. It's not just plain gforth, it has some Android interfaces.
!forth -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 17-Aug-2017 10:02:34 UTC Hallå Kitteh In the context of #stage0 , this paper is suddenly relevant (again).
> Putting Lisp on Forth base
Would be cool if this turns out to actually be referenced in the stage0 work.
http://dl.acm.org/citation.cfm?id=59429
!forth -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 17-Aug-2017 01:09:58 UTC Hallå Kitteh @jjg @alanz Found in the comments: Lots of !forth articles in this 1980 Byte Magazine.
https://archive.org/details/byte-magazine-1980-08
Holy moley, 300 pages? And it apparently came out at least 8 times a year, so I'm guessing it was monthly.
There's a great Microsoft advertisement for their various language implementations for CP/M (no Forth), and a column subtweeting Microsoft for Bill's stance on software piracy. (both somewhere around the page 90 mark, magazine page numbering) -
awg (awg@gnusocial.de)'s status on Tuesday, 15-Aug-2017 03:32:22 UTC awg !forth in a conventional compiler (even in Forth), rules about the use of plaintext syntax and whitespace are used to help the compiler determine the programmer's intentions in his/her code. this makes for a fundamentally simpler editor but a more complex compiler responsible not only for generating executable code but policing the programmer for unambiguous input.
in colorForth(/ArrayForth), the editor employs colour as syntax and source is packed in a form readily understandable by the compiler while the programmer enters it. this makes for a more complex editor but fundamentally a simpler compiler, as the latter -- no longer necessarily responsible for trying to determine programmer's intentions -- now only processes unambiguous directives given in the packed code (eg, so begins a new word, this word is to be run when this source block is compiled, this is the name of a variable, etc).
there are not many computing devices still in existence that don't second-guess their operators. -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 15-Aug-2017 01:39:17 UTC Hallå Kitteh Here Chuck is talking about how he got tired of all the various loop construct and says that what he is doing today is just recurse into yourself if you need a loop.
What he is describing is basically a named let and a tail call. Very cool. The similarities, or maybe duality, of !scheme and !forth have never been more obvious.
> (Jeff) You might point out that your semicolon after WORD results in tail recursion and converting the call in WORD to a jump and that is how it functions.
> (Chuck) So there is no reason to make that a call since you are never going to go anywhere afterwards so you just make that jump. In fact in all my latest Forths semicolon kind of meant either return or jump depending on the context and it's optimized in the compiler to do that. It's a very simple look back optimization that actually saves a very important resource, the return stack.
http://www.ultratechnology.com/1xforth.htm -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Tuesday, 15-Aug-2017 01:19:52 UTC Hallå Kitteh A strong opinion on !forth :
> Many programmers choose to reject the idea that Forth is the OS. Instead they prefer to implement Forth as a conventional programming language on top of the operating system of their choice. By doing so they violate several of the original definitions of Forth. What they have is not longer a complete system, instead they have choosen to return to the multi-level nightmare.
http://www.ultratechnology.com/4thdef.htm -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Monday, 14-Aug-2017 08:01:35 UTC Hallå Kitteh @roka @awg "multiple" is sort of an understatement. It feels like the only language that has more implementations is !forth . :-)
Many people like #racket, as it has an IDE that is very helpful to newcomers. #Chez is performant and complete. I quite like #guile as it's GNU, used for #guix and has some intriguing new async stuff I'd like to play with.
A decade ago when I did #SICP in uni, the course recommended Racket (then Dr Scheme) or MIT Scheme, but I used Guile because it had a very POSIX-y and familiar command line and I wrote my lab exercises with Makefiles running the tests.
Back then I also had a look at #gauche (also very script-y and POSIX-y) and #scheme48, which integrates well with SMILE in emacs. These days there's #geiser for guile, which is likely to be the best emacs+Scheme interactive mode out there.
As far as I'm concerned, https://wingolog.org/archives/2013/01/07/an-opinionated-guide-to-scheme-implementations is the canonical "which scheme?" page. -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Wednesday, 02-Aug-2017 05:11:53 UTC Hallå Kitteh !forth CPUs!
> the documentation of the GA144 might also make for fun reading, since this is still in production. http://www.greenarraychips.com/ -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Monday, 31-Jul-2017 09:52:38 UTC Hallå Kitteh @ckeen Oh! Awesome, thanks!
!forth
http://thinking-forth.sourceforge.net/ -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Monday, 31-Jul-2017 03:14:29 UTC Hallå Kitteh @cwebber @tomas @loke @alanz @arunisaac
http://bootstrappable.org/projects.html explains Mes better in English than the repo or the announcement does, and it also clarifies that mes and stage0 are two different things.
Stage0 apparently starts from almost nothing, goes on with !forth then does some variant of !lisp ... more to study at http://git.savannah.nongnu.org/cgit/stage0.git and http://savannah.nongnu.org/news/?group_id=11718 -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 20-Apr-2017 15:15:48 UTC Hallå Kitteh @solderpunk I still haven't had my !forth baptism. I'm just admiring it from afar. :-) -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 20-Apr-2017 08:17:52 UTC Hallå Kitteh @thatbrickster Every language ever should be bootstrapped from a small machine code kernel that builds a !forth kernel that then builds the real thing. -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 06-Apr-2017 07:19:41 UTC Hallå Kitteh @vertigo #picolisp is pretty !forth-like in a sense. Its a very small kernel, it bridges well with machine code and most of it is written in picolisp. But the kernel is in assembler and quite tied to the hardware. pico for x86-64 an x86 even have different features. I guess that makes it both easy and hard to port. Tiny kernel, but you need to rewrite it all each time. -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Saturday, 25-Feb-2017 12:01:46 UTC Hallå Kitteh @limbclock Take a look at !forth. That's as real-world as you get.