Go to file
retropikzel 2d62b68241 Bug fixes 2024-09-15 10:27:15 +03:00
docs Clean repo of old test scripts 2024-09-03 15:27:09 +03:00
old-tests Move to running tests with scheme_runner 2024-09-03 15:15:15 +03:00
retropikzel/r7rs-pffi/version Bug fixes 2024-09-15 10:27:15 +03:00
.gitignore Move to running tests with scheme_runner 2024-09-03 15:15:15 +03:00
Dockerfile Move scheme runner code here as it's the only repo that needs it 2024-09-05 11:27:07 +03:00
Jenkinsfile Discard old builds 2024-09-06 08:56:58 +03:00
LICENSE Fix tests, add pffi-os-name 2024-07-31 21:14:38 +03:00
Makefile Working on Chicken bugs, backup 2024-09-14 15:46:03 +03:00
README.md Update readme 2024-09-03 15:47:42 +03:00
composition.scm Move to running tests with scheme_runner 2024-09-03 15:15:15 +03:00
curl.dll Fix tests, add pffi-os-name 2024-07-31 21:14:38 +03:00
kawa.jar Added most of Kawa support 2024-05-06 20:45:31 +03:00
mkdocs.yml Update readme, improve documentation 2024-08-25 16:39:05 +01:00
scheme_runner Make to work in jenkins 2024-09-06 07:27:33 +03:00
test.scm Bug fixes 2024-09-15 10:27:15 +03:00

README.md

Portable Foreign Function Interface for R7RS schemes

Foreign function interface that is supported on multiple R7RS Sceheme implementations.

Note that this software is in alpha stage. That said the interface should not be changing anymore.

Any help in form of constructive advice and bug reports are appreciated.

Documentation or run mkdocs serve or see docs/.

Issue tracker

Maling lists

For documentation see retropikzel.neocities.org/r7rs-pffi or run mkdocs serve or see or docs/ directory.

Goals

  • Support only R7RS implementations
    • Needs to have cond-expand and library support atleast (propably much more)
  • Same interface on all implementations
    • Some things that are procedures on one implementation are macros on other, but they must behave the same

Non goals

  • To support all R7RS implementations
  • To have every possible FFI feature
  • Compiling of C code at any point
    • That is no stubs, no C code generated by the library and so on

Support tiers

Support is defined in tiers, each tier has short explanation about it after the title.

Currently the interface of the library is okay. Now work needs to be done to make tests and see that each implementation passes those tests. This will be done in tiered order starting from tier 1.

Tier 1

  • Chicken
  • Guile
  • Kawa
    • Needs at least java version 22
    • Needs jvm flags:
      • --add-exports java.base/jdk.internal.foreign.abi=ALL-UNNAMED
      • --add-exports java.base/jdk.internal.foreign.layout=ALL-UNNAMED
      • --add-exports java.base/jdk.internal.foreign=ALL-UNNAMED
      • --enable-native-access=ALL-UNNAMED
  • Sagittarius
  • Racket

Tier 2

  • Gambit
    • Propably able to support everything but so annoying to deal with that it's currently in tier 2
    • Still needs work
  • STKlos
    • No callback support
    • Still needs work
  • Cyclone
    • No callback support
    • Still needs work

Tier 3

  • LIPS
    • Waiting for implementation to have cond-expand and library support
    • Will only work on nodejs
  • Biwascheme
    • Waiting for implementation to have cond-expand and library support
    • Will only work on nodejs

Tier 4

Support needs to be investigated.

Tier 5

Support maybe possible/dreaming about.

  • Airship
  • Other gambit targets
    • Gambit compiles to different targets other than C too, for example Javascript. It would be cool and interesting to see if this FFI could also support some of those

Tier 6

Not supported currently, and may never be.

  • Chibi
    • FFI requires C code
  • MIT-Scheme
    • FFI requires C code
  • tr7
    • FFI requires C code
  • Gauche
    • FFI requires C code
  • s7
    • No library support
    • Might have other things missing too
  • Loko
    • Desires no C interop, I can respect that