| 1 | README for pForth - a Portable ANS-like Forth written in ANSI 'C'\r |
| 2 | \r |
| 3 | by Phil Burk\r |
| 4 | with Larry Polansky, David Rosenboom and Darren Gibbs.\r |
| 5 | Support for 64-bit cells by Aleksej Saushev.\r |
| 6 | \r |
| 7 | Last updated: May 20, 2010 V26\r |
| 8 | \r |
| 9 | Code for pForth is maintained on Google at:\r |
| 10 | http://code.google.com/p/pforth/\r |
| 11 | \r |
| 12 | Documentation for pForth at:\r |
| 13 | http://www.softsynth.com/pforth/\r |
| 14 | \r |
| 15 | For technical support please use the pForth forum at:\r |
| 16 | http://groups.google.com/group/pforthdev\r |
| 17 | \r |
| 18 | The author is available for customization of pForth, porting to new\r |
| 19 | platforms, or developing pForth applications on a contractual basis.\r |
| 20 | If interested, contact Phil Burk at:\r |
| 21 | http://www.softsynth.com/contacts.php\r |
| 22 | \r |
| 23 | -- LEGAL NOTICE -----------------------------------------\r |
| 24 | \r |
| 25 | The pForth software code is dedicated to the public domain,\r |
| 26 | and any third party may reproduce, distribute and modify\r |
| 27 | the pForth software code or any derivative works thereof\r |
| 28 | without any compensation or license. The pForth software\r |
| 29 | code is provided on an "as is" basis without any warranty\r |
| 30 | of any kind, including, without limitation, the implied\r |
| 31 | warranties of merchantability and fitness for a particular\r |
| 32 | purpose and their equivalents under the laws of any jurisdiction.\r |
| 33 | \r |
| 34 | -- Contents of SDK --------------------------------------\r |
| 35 | \r |
| 36 | build - tools for building pForth on various platforms\r |
| 37 | build/win32/vs2005 - Visual Studio 2005 Project and Solution\r |
| 38 | build/unix - Makefile for unix\r |
| 39 | \r |
| 40 | csrc - pForth kernel in ANSI 'C'\r |
| 41 | csrc/pf_main.c - main() application for a standalone Forth\r |
| 42 | csrc/stdio - I/O code using basic stdio for generic platforms\r |
| 43 | csrc/posix - I/O code for Posix platform\r |
| 44 | csrc/win32 - I/O code for basic WIN32 platform\r |
| 45 | csrc/win32_console - I/O code for WIN32 console that supports command line history\r |
| 46 | \r |
| 47 | fth - Forth code\r |
| 48 | fth/util - utility functions\r |
| 49 | \r |
| 50 | -- How to build pForth ------------------------------------\r |
| 51 | \r |
| 52 | See pForth reference manual at:\r |
| 53 | \r |
| 54 | http://www.softsynth.com/pforth/pf_ref.htm\r |
| 55 | \r |
| 56 | -- How to run pForth ------------------------------------\r |
| 57 | \r |
| 58 | Once you have compiled and built the dictionary, just enter:\r |
| 59 | pforth\r |
| 60 | \r |
| 61 | To compile source code files use: INCLUDE filename\r |
| 62 | \r |
| 63 | To create a custom dictionary enter in pForth:\r |
| 64 | c" newfilename.dic" SAVE-FORTH\r |
| 65 | The name must end in ".dic".\r |
| 66 | \r |
| 67 | To run PForth with the new dictionary enter in the shell:\r |
| 68 | pforth -dnewfilename.dic\r |
| 69 | \r |
| 70 | To run PForth and automatically include a forth file:\r |
| 71 | pforth myprogram.fth\r |
| 72 | \r |
| 73 | -- How to Test PForth ------------------------------------\r |
| 74 | \r |
| 75 | You can test the Forth without loading a dictionary\r |
| 76 | which might be necessary if the dictionary can't be built.\r |
| 77 | \r |
| 78 | Enter: pforth -i\r |
| 79 | In pForth, enter: 3 4 + .\r |
| 80 | In pForth, enter: loadsys\r |
| 81 | In pForth, enter: 10 0 do i . loop\r |
| 82 | \r |
| 83 | PForth comes with a small test suite. To test the Core words,\r |
| 84 | you can use the coretest developed by John Hayes.\r |
| 85 | \r |
| 86 | Enter: pforth\r |
| 87 | Enter: include tester.fth\r |
| 88 | Enter: include coretest.fth\r |
| 89 | \r |
| 90 | To run the other tests, enter:\r |
| 91 | \r |
| 92 | pforth t_corex.fth\r |
| 93 | pforth t_strings.fth\r |
| 94 | pforth t_locals.fth\r |
| 95 | pforth t_alloc.fth\r |
| 96 | \r |
| 97 | They will report the number of tests that pass or fail.\r |