Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
atr
fig-FORTH1.4S-1.atr 92.2 kB 1 05-Jul-2016 10:53 Roland B. Wassenberg fig-FORTH1.4S-1
atr
fig-FORTH1.4S-2.atr 92.2 kB 1 05-Jul-2016 10:53 Roland B. Wassenberg fig-FORTH1.4S-2

This page (revision-72) was last changed on 01-May-2018 03:30 by Roland B. Wassenberg  

This page was created on 20-Feb-2010 21:56 by Carsten Strotmann

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 4 changed one line
Forth is a programming language that uses a stack-based metaphor in an effort to reduce memory requirements as much as possible. In contrast to languages like [Basic], the parser never has to "look ahead" to find additional data in order to see if a command is properly entered, any data it could need has to be pushed onto the stack as well.
Forth is a programming language that uses a stack-based metaphor in an effort to reduce memory requirements as much as possible. In contrast to languages like [Basic], the parser never has to "look ahead" to find additional data in order to see if a command is properly entered, any data it could need has to be pushed onto the stack as well. This greatly reduces the size of the parser, and as a result, leaves more room free for programs.
At line 6 changed one line
The downside to this approach is that it makes the language difficult to understand by mere mortals, and as a result, Forth was subject to perhaps one of the longest running fanboi wars since APL was invented. Constantly derided by practically everyone in the industry, it saw some interest in spite of this, but little commercial software emerged. The singular exception may be the PostScript system found in printers as the underlying basis for the PDF format, which is essentially a version of Forth modified for graphics output.
Another key aspect of the language was Forth's inherently multitasking design. The program could set up separate stacks and feed different code into each one. The Forth kernel would run each of these stacks in turn, so all Forth programs had access to these features. This made writing multithreaded code very easy, so one could, for instance, have a thread reading the joystick as it moved, and then read that value in a game loop in another stack.
At line 8 added 2 lines
The downside to the stack-based approach is that it makes the language difficult to understand by mere mortals. Even tutorials purporting to show how simple it was often ended in an unreadable mess. As a result, Forth was subject to perhaps one of the longest running fanboi wars since APL was invented. Constantly derided by practically everyone in the industry, it saw some interest in spite of this, but little commercial software emerged. The singular exception is the PostScript system, which is essentially a version of Forth modified to produce graphics output.
Version Date Modified Size Author Changes ... Change note
72 01-May-2018 03:30 6.695 kB Roland B. Wassenberg to previous
71 28-Apr-2018 15:44 6.695 kB Maury Markowitz to previous | to last
70 28-Apr-2018 15:38 6.295 kB Maury Markowitz to previous | to last
69 28-Apr-2018 15:36 6.27 kB Maury Markowitz to previous | to last
68 26-Apr-2018 22:31 4.923 kB Maury Markowitz to previous | to last
67 26-Apr-2018 22:19 4.336 kB Maury Markowitz to previous | to last
66 29-Aug-2017 04:50 3.271 kB Roland B. Wassenberg to previous | to last
65 25-Feb-2017 16:55 3.292 kB Carsten Strotmann to previous | to last
64 05-Jul-2016 10:56 3.153 kB Roland B. Wassenberg to previous | to last
63 02-Jul-2016 01:07 3.103 kB Roland B. Wassenberg to previous | to last
62 01-Jul-2016 18:40 3.062 kB Roland B. Wassenberg to previous | to last
61 23-Jan-2014 18:28 3.048 kB Carsten Strotmann to previous | to last
« This page (revision-72) was last changed on 01-May-2018 03:30 by Roland B. Wassenberg