Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Racket (MzScheme) CS is not supported #9148

Open
dertuxmalwieder opened this issue Nov 17, 2021 · 3 comments
Open

Racket (MzScheme) CS is not supported #9148

dertuxmalwieder opened this issue Nov 17, 2021 · 3 comments

Comments

@dertuxmalwieder
Copy link
Contributor

Steps to reproduce

  1. Build Racket from source, using MSVC2019:
cd src/worksp
./msvcprep.bat amd64
./build-cs.bat
  1. Try to find scheme.h and schvers.h, both of which if_mzsch.h tries to #include.
  2. They aren't there, so I cannot build Vim.

Expected behaviour

Racket "CS", the new standard version of Racket based on Chez Scheme, should be supported. Currently, I'll have to build the "legacy" Racket version (build.bat instead of build-cs.bat) which will probably not be around forever,

Operating system

Windows 10, VS2019

Version of Vim

master branch

Logs and stack traces

No response

@k-takata
Copy link
Member

It seems that the "CS" version has totally different APIs from the legacy "BC" version.

@benknoble
Copy link
Contributor

cc @mflatt : I think @k-takata is right. Curious about what can be done so that vim can support Racket on CS, but I imagine (modulo Racket making changes) the straightest path forward is to modify vim to work with either BC or CS, whichever it detects?

@mflatt
Copy link

mflatt commented Nov 18, 2021

@benknoble From a quick look at if_mzsch.c, it may be simpler to treat CS as a different language and create if_racket.c. So much of what if_mzsch.c does is through a C-level API that doesn't exist in Racket CS. I think a CS binding would will need to go through racket_eval and use the Chez Scheme FFI to create Scheme functions that get back to C functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants