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

Consider using closer-mop #7

Open
dieggsy opened this issue Mar 6, 2025 · 2 comments
Open

Consider using closer-mop #7

dieggsy opened this issue Mar 6, 2025 · 2 comments

Comments

@dieggsy
Copy link
Collaborator

dieggsy commented Mar 6, 2025

sql/base/package.lisp does a bunch of implementation conditionals to import MOP symbols. It may be cleaner to use closer-mop instead. A potential issue is closer-mop no longer lists cmucl as actively supported, though it still ships a closer-cmu.lisp file (which may or may not work).

@dieggsy
Copy link
Collaborator Author

dieggsy commented Mar 6, 2025

To get around CMU maybe not being supported, we could just keep importing-from for both closer-mop and cmucl, in which case symbols should stay the same, and we can cover other supported implementations with closer-mop.

It would be nice not to have to import and just use package qualified c2mop: symbols, though.

@dieggsy
Copy link
Collaborator Author

dieggsy commented Mar 10, 2025

As it turns out, I don't think CMUCL has 64-bit support:

It seems likely this is the reason closer-mop no longer officially supports it.

Given this (and the increasing scarcity of operating systems supporting 32-bit architectures), we could stop officially supporting CMUCL until further updates on their end?

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

No branches or pull requests

1 participant