version 1.47, 1995/11/09 19:37:03
|
version 1.48, 1995/12/23 16:21:58
|
Line 24
|
Line 24
|
\ |
\ |
\ |
\ |
\ |
\ |
\ This file contains instructions in the following format: |
\ This file contains primitive specifications in the following format: |
\ |
\ |
\ forth name stack effect category [pronunciation] |
\ forth name stack effect category [pronunciation] |
\ [""glossary entry""] |
\ [""glossary entry""] |
Line 32
|
Line 32
|
\ [: |
\ [: |
\ Forth code] |
\ Forth code] |
\ |
\ |
\ The pronunciation is also used for forming C names. |
\ prims2x is pedantic about tabs vs. blanks. The fields of the first |
|
\ line of a primitive are separated by tabs, the stack items in a |
|
\ stack effect by blanks. |
|
\ |
|
\ Both pronounciation and stack items (in the stack effect) must |
|
\ conform to the C name syntax or the C compiler will complain. |
\ |
\ |
\ |
\ |
\ |
\ These specifications are automatically translated into C-code for the |
\ These informations are automatically translated into C-code for the |
|
\ interpreter and into some other files. I hope that your C compiler has |
\ interpreter and into some other files. I hope that your C compiler has |
\ decent optimization, otherwise the automatically generated code will |
\ decent optimization, otherwise the automatically generated code will |
\ be somewhat slow. The Forth version of the code is included for manual |
\ be somewhat slow. The Forth version of the code is included for manual |