Menu

Future Changes

These changes, as of this writing, are not listed in any particular order of importance. They will be updated, reordered, etc. as time goes on

  • Update the words that call ffi:type:select so that they are wrapped in Forth words that yield the right result rather than use constants as seen in the scriptwrap.sh and call_puts.fth example files.
    • There's some work on the way to take care of this. It hasn't been uploaded yet.
  • Figure out why strings sometimes hang around in instead of being disappeared as they should. Possibly due to not clearing PAD or some other Forth buffer?
  • Currently the only way to get shell input into an OspreyForth script is to wrap it in a shell script (see examples/scriptwrap.sh). Basically, a shell script takes the input arguments and writes them into an OspreyForth script. This needs to be changed.
  • Create bridge code to the C99 library and incorporate that code into the startup code of the interpreter
  • Add JSON and possibly XML-RPC C libraries to the runtime for networking use
  • Possibly create bridge code to Apple's Objective-C and GNUStep's Objective-C 2 runtimes
  • Possibly create bridge code for Apache's APR library for networking use
  • Create example code
    • There's some work on the way to take care of this. It hasn't been uploaded yet.
  • Update the banner line of the interpreter so that when it runs it doesn't announce itself as "PForth", to avoid confusion.
  • Replace the banner line to announce itself as "OspreyForth" and continue with licenses for PForth, OspreyForth and the Entities code by Christoph Gärtner

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.