All geek questions in one place

CLisp: "use-package" resolves conflicts non-interactively

I am trying to use parenscript in GNU common lisp to compile a lisp file in javascript.

I found that using the PS symbol "@" does not work if I try to use its prefix ("ps: @"). However, if I use REPL and run (use-package: ps) before trying to compile the lisp file, everything will work as expected (and I don't need to use prefixes).

The problem is that the PS package contains conflicting characters, for example:

*** - (USE-PACKAGE (#<PACKAGE PARENSCRIPT>) #<PACKAGE COMMON-LISP-USER>): 2 name conflicts remain Which symbol with name "CHAIN" should be accessible in #<PACKAGE COMMON-LISP-USER>? The following restarts are available: PARENSCRIPT :R1 #<PACKAGE PARENSCRIPT> COMMON-LISP-USER :R2 #<PACKAGE COMMON-LISP-USER> ABORT :R3 Abort main loop

I can resolve this interactively by choosing: r1, but when I try to put this step in my script, it just does the bail (since it is non-interactive, it does not give me a choice which restart to use)

I would say (in my script) “just use the PS version of all the characters encountered”, but I can’t figure out how to do this.

It would also be nice if I could say (as it would be in python): "from PS import chain, @, (etc.)" - an indication of each character that I want to import manually.

+4
source share
1 answer

Instead of working in the COMMON-LISP -USER package, make your own with DEFPACKAGE:

 (defpackage #:my-awesome-program (:use #:cl #:parenscript)) (in-package #:my-awesome-program) ; your code here

COMMON-LISP -USER can include all kinds of characters for a particular implementation.

You can also use SHADOWING-IMPORT to retrieve individual characters, overriding what might already be visible at the moment in the package, for example

 (shadowing-import 'ps:*)
+8
source

Source: https://habr.com/ru/post/1303358/

More articles:


All Articles