In order to accommodate the needs of various embedded systems certain features of the Embeddable Forth Command Interpreter are configurable at compile time. The idea is to not burden a system with features it does not use. In fact it might be highly undesirable to have features that are not absolutely necessary e.g. if the software is used in such a product that requires extensive validation for safety or other regulation purposes. In general features that are not used just should not be there at all.<\/p>\n
Other features such as the maximum size of the dictionary and stack space are highly usage dependent.<\/p>\n
Compile time configuration is done by editing the C header file forth_features.h before compiling the system.<\/p>\n
\r\n\/\/ The size of the terminal buffer.\r\n#define TIB_SIZE 256\r\n\r\n\/\/ The size of the Forth Dictionary in CELLs.\r\n\/\/ Because of the execution model it should be\r\n\/\/ less than 64K cells (256 KB on a 32bit system).\r\n#define FORTH_DICTIONARY_SIZE 4096\r\n\r\n\/\/ The number of user defined per execution thread variables\r\n\/\/ (known as USER variables in Forth parlance).\r\n\/\/ #undef this to disable USER variables altogether.\r\n#define FORTH_USER_VARIABLES 256\r\n\r\n\/\/ #undef this if you don't want file access words.\r\n#define FORTH_INCLUDE_FILE_ACCESS_WORDS 1\r\n\r\n\/\/ #undef this if you don't want memory allocation words.\r\n#define FORTH_INCLUDE_MEMORY_ALLOCATION_WORDS 1\r\n\r\n\/\/ Some macros to allocate the C style (0 terminated) strings\r\n\/\/ for file names.\r\n#if defined(FORTH_INCLUDE_FILE_ACCESS_WORDS)\r\n# define FORTH_FILE_INPUT_BUFFER_LENGTH 256\r\n# define FORTH_ALLOCATE_CNAME(PTR, LEN) (strndup)((PTR), (LEN))\r\n# define FORTH_FREE_CNAME(X) free((X))\r\n#endif\r\n\r\n\/\/ #define this if you don't want the Forth compiler (interpreter only).\r\n#undef FORTH_DISABLE_COMPILER\r\n\r\n\/\/ #undef this if you don't want the word MS.\r\n#define FORTH_INCLUDE_MS 1\r\n\/\/ #undef this if you don't want the word TIME&DATE\r\n#define FORTH_INCLUDE_TIME_DATE 1\r\n\r\n\/\/ #undef this to disable stack underflow\/overflow checking.\r\n#define FORTH_STACK_CHECK_ENABLED\r\n\r\n\/\/ #define this to disable ALL double number and mixed arithmetic,\r\n\/\/ no D+ -es, M+ -es or *\/-s, not even #.\r\n#undef FORTH_NO_DOUBLES\r\n\r\n\/\/ #undef this if you do not want to allow C-style hex numbers\r\n\/\/ that start with 0x\r\n#define FORTH_ALLOW_0X_HEX 1\r\n\r\n\/\/ If the application requires extra fields in the run time context\r\n\/\/ #define this to list them.\r\n\/\/ See the telnet implementation in the ZedBoard example for an example.\r\n#undef FORTH_APPLICATION_DEFINED_CONTEXT_FIELDS\r\n<\/pre>\nRun-time Configurable fields in the Context<\/h2>\n
The Run time context passed to the function forth()<\/strong> has several per thread fields that need to be properly initialized. A full list can be obtained from the source file forth.h<\/em>. The most noteworthy fields that need to be initialized by the application are the following:<\/p>\n
\n
- Sp<\/strong>, sp0<\/strong>, sp_min<\/strong> and sp_max<\/strong>: The current, initial, minimum and maximum values of the data stack pointer.<\/li>\n
- Rp<\/strong>, rp0<\/strong>, rp_min<\/strong> and rp_max<\/strong>: The current, initial, minimum and maximum values of the return stack pointer.<\/li>\n
- Terminal_width<\/strong>: The width of the terminal in characters.<\/li>\n
- Terminal_height<\/strong>: The height of the terminal in characters.<\/li>\n<\/ul>\n
The following are function pointers that implement terminal I\/O operation and can in fact vary from per thread of execution if e.g. one thread is talking to a serial line and another one is talking to a network connection. They are the implementation details of the Forth words listed in the corresponding comment. There really isn’t any one size fits all solution as different embedded systems might use drastically different means to talk to the outside world (if at all) and some operations might be unimplementable on some of them.<\/p>\n
\r\n\/\/ PAGE -- If the device cannot do it set to to 0.\r\nint (*page)(struct forth_runtime_context *rctx);\r\n\r\n\/\/ AT-XY -- If the device cannot do it set to to 0. \r\nint (*at_xy)(struct forth_runtime_context *rctx, forth_cell_t x, forth_cell_t y); \r\n \r\n\/\/ TYPE\r\nint (*write_string)(struct forth_runtime_context *rctx, const char *str, forth_cell_t length); \r\n \r\n\/\/ CR\r\nint (*send_cr)(struct forth_runtime_context *rctx); \r\n \r\n\/\/ ACCEPT\r\nforth_scell_t (*accept_string)(struct forth_runtime_context *rctx, char *buffer, forth_cell_t length); \r\n \r\n\/\/ KEY\r\nforth_cell_t (*key)(struct forth_runtime_context *rctx); \r\n \r\n\/\/ KEY?\r\nforth_cell_t (*key_q)(struct forth_runtime_context *rctx); \r\n \r\n\/\/ EKEY\r\nforth_cell_t (*ekey)(struct forth_runtime_context *rctx); \r\n \r\n\/\/ EKEY?\r\nforth_cell_t (*ekey_q)(struct forth_runtime_context *rctx); \r\n \r\n\/\/ EKEY>CHAR\r\nforth_cell_t (*ekey_to_char)(struct forth_runtime_context *rctx, forth_cell_t ekey);\r\n \r\n<\/pre>\nThere are several other filed in the runtime context but they are either internal to the Forth system or should be always initialized the same way for other reasons. Probably best is to just follow the examples in the source code.<\/p>\n","protected":false},"excerpt":{"rendered":"
In order to accommodate the needs of various embedded systems certain features of the Embeddable Forth Command Interpreter are configurable at compile time. The idea is to not burden a system with features it does not use. In fact it … Continue reading