Skip to content

Please add cl-fxml #1969

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

Closed
Goheeca opened this issue Jan 18, 2021 · 7 comments
Closed

Please add cl-fxml #1969

Goheeca opened this issue Jan 18, 2021 · 7 comments
Labels

Comments

@Goheeca
Copy link

Goheeca commented Jan 18, 2021

https://github.com/Goheeca/cl-fxml

Loads fine and works on SBCL, and ABCL.

I also tried CLISP 2.49.92 (2018-02-18), but the dependency named-readtables failed to load:

*** - Error while trying to load definition for system named-readtables from pathname /home/goheeca/quicklisp/dists/quicklisp/software/named-readtables-20201220-git/named-readtables.asd:
      REINITIALIZE-INSTANCE: illegal keyword/value pair :MAILTO, "[email protected]" in argument list.
      The allowed keywords are (:NAME :VERSION :IN-ORDER-TO :DO-FIRST :PARENT :PATHNAME :AROUND-COMPILE :ENCODING
      :PROPERTIES :COMPONENTS :IF-COMPONENT-DEP-FAILS :DEFAULT-COMPONENT-CLASS :DESCRIPTION :LONG-DESCRIPTION :AUTHOR :MAINTAINER :LICENCE :LICENSE :SOURCE-FILE :DEFSYSTEM-DEPENDS-ON)
@Hexstream
Copy link
Contributor

CLISP has not seen an official release in more than a decade, so no need to worry about supporting it, in my view. We already have plenty of actively officially supported implementations to worry about.

(Yes, I am aware that there is an unofficial fork of CLISP somewhere.)

@xach
Copy link
Contributor

xach commented Jan 18, 2021

CLISP failure is not a deal-breaker.

@phoe
Copy link

phoe commented Jan 18, 2021

The CLISP failure you mention sounds like something that could be solved by updating ASDF to a newer version. (AFAIK the last CLISP release still ships with ASDF 2 by default.)

If you feel like spending a while on that, you could try upgrading your local CLISP installation to ASDF 3.4+ (e.g. by downloading and loading https://common-lisp.net/project/asdf/archives/asdf.lisp into it) and see if your system and its dependencies load correctly then.

@xach
Copy link
Contributor

xach commented Jan 18, 2021

CLISP does not include ASDF at all, so it's likely using the Quicklisp fallback 2.26.

@phoe
Copy link

phoe commented Jan 18, 2021

OK - that's plausible. (It's likely a question for a separate issue, is it feasible/possible for Quicklisp to bump up its fallback ASDF version to 3.x? Why not?)

@Goheeca
Copy link
Author

Goheeca commented Jan 19, 2021

After loading the linked asdf into CLISP, everything worked fine.

@phoe
Copy link

phoe commented Jan 19, 2021

Good - it's an issue of an old ASDF, then, and nothing wrong with your system.

quicklisp added a commit that referenced this issue Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants