ChipMaster's bwBASIC This also includes history going back to v2.10. *WARN* some binary files might have been corrupted by CRLF.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

76 lines
2.4 KiB

  1. Some Notes on Installation of the Bywater BASIC Interpreter:
  2. -----------------------------------------------------------
  3. 0. Quick-Start Guide For Compiling
  4. To use the default configuration (which is reasonable for most situations):
  5. On Unix, type "configure; make".
  6. On Android using CCTools, type "ash ./xxc.sh".
  7. If you are using GCC with the default libraries on a flavor of Unix,
  8. then perhaps "gcc -DHAVE_ISNAN -o bwbasic -lm -ansi bw*.c"
  9. On MSDOS, add all the bw*.c file to a new project.
  10. You can skip the rest of this file unless you want to customize the
  11. BASIC dialect that is supported, or something goes wrong in the
  12. above commands.
  13. 1. Compiler Requirements
  14. ANSI C.
  15. 2. Configuration of header files
  16. You may need to examine file "bwbasic.h" to make important
  17. changes for specific hardware and compiler configurations.
  18. 3. Makefiles
  19. Several compiler-specific makefiles are provided AS-IS,
  20. and have not been tested with version 3.00.
  21. "makefile" will compile the
  22. program on Unix-based computers.
  23. "makefile.qcl" is for the Microsoft QuickC (tm).
  24. I have also compiled the program utilizing
  25. Borland's Turbo C++ (tm) and Pacific C (tm)
  26. on DOS-based machines.
  27. 4. Implementations
  28. TTY is the base implementation and presumes a simple
  29. TTY-style environment, with all keyboard and screen input
  30. and output directed through stdin and stdout. All commands,
  31. functions and operators should be available in the TTY
  32. implementation, even when they do nothing. For example,
  33. CLS, COLOR and LOCATE do nothing when OPTION TERMINAL NONE
  34. is specified. This allows exising classic BASIC applications
  35. to execute.
  36. 5. Adding Commands and Functions
  37. Follow the rules in "Implementation rules for functions and commands";
  38. the majority of BASIC commands are actually intrinsic functions.
  39. Adding a new command is more work than adding a new function.
  40. In order to add a new command to bwBASIC:
  41. Search for C_WRITE and bwb_WRITE,
  42. and add your command's eqivalent information in the same places.
  43. The last command's unique number should equal NUM_COMMANDS.
  44. Adding a new function is easier:
  45. Search for F_ABS_X_N,
  46. and add your function's equivalent information in the same places.
  47. The last function's unique number should equal NUM_FUNCTIONS.