Fix some typos, h/t @j4james
Chris Pressey
6 years ago
| 18 | 18 | Most likely the most unique element of Befunge-93 programming is the |
| 19 | 19 | Program Counter (PC.) In almost all computer programming languages, the |
| 20 | 20 | program counter is continually moving forward through the program, |
| 21 | occassionally jumping to another spot in the code (but continuing | |
| 21 | occasionally jumping to another spot in the code (but continuing | |
| 22 | 22 | forward thereafter, nonetheless.) |
| 23 | 23 | |
| 24 | 24 | The PC in Befunge-93, however, is subject to different rules. It may go |
| 74 | 74 | the upper-left of the torus and is initially oriented to execute |
| 75 | 75 | rightward. |
| 76 | 76 | |
| 77 | NB. If the stack is be empty when you pop something off, be warned that | |
| 77 | NB. If the stack is empty when you pop something off, be warned that | |
| 78 | 78 | this will *not* generate an underflow! It will simply push a 0 value |
| 79 | 79 | onto the stack. Hope you can live with it! |
| 80 | 80 | |
| 211 | 211 | |
| 212 | 212 | The last two commands that need to be explained are the ones that allow |
| 213 | 213 | you to examine and change the contents of the torus where the program is |
| 214 | stored. This 'playfield' can be used for auxilliary storage when the | |
| 214 | stored. This 'playfield' can be used for auxiliary storage when the | |
| 215 | 215 | stack alone will not suffice, but keep in mind that it also contains the |
| 216 | 216 | running program. |
| 217 | 217 | |