armedbear-devel

armedbear-devel@common-lisp.net

1199 discussions

Considering resignation as maintainer
by Robert Goldman 10 Jan '22

10 Jan '22

I have discovered that Stas Bokuraev is continuing to refuse to update Edi packages to modern ASDF system-naming. This would not be bad in and of itself, because these are open source systems, and they can be forked. What *is* bad is that he has publicly stated that he is doing this hoping that the resulting warnings will break people's systems and thus cause them to get angry and complain to me about ASDF checking system names. What is even worse is that the CL community tacitly accepts this as normal behavior. I would like to see the CL open source community pause and consider what constitutes a healthy community. I don't believe that someone trying to break things in order to pressure a volunteer maintainer of infrastructure is something that a healthy community should accept. If the community prefers a more rough-and-tumble approach, I can accept that, but if so it's time for the community to find an ASDF maintainer who is more in harmony with the values it (at least implicitly) espouses.

2 1

(rationalize) works differently in ABCL
by Andrew Sengul 27 Nov '21

27 Nov '21

I've been doing operations that require me to rationalize floats, and I've found that (rationalize 2.3d0)gives very different output in ABCL compared SBCL and CCL. Floats can have any number of valid rational conversions but I'd expect a good algorithm for this conversion to find 23/10 rather than the huge numerators and denominators that get produced. It appears that the (rationalize) in ABCL is using the same algorithm as (rational) does in other CLs. Does (rationalize) just pass through to (rational) in ABCL? Would it make sense for ABCL to adopt the implementation of this function used by other CLs? Thanks. Andrew

1 0

One more question - compiling large code
by Andrew Sengul 23 Nov '21

23 Nov '21

I was just trying to compile a system containing macros that generate a large amount of code. I got this error: Compiled function can't be loaded: org.armedbear.lisp.demo_tmpHVF0FTR3_246 from org.armedbear.lisp.Pathname@2a31c2ec Does anyone know the likely reason for this? The code I'm compiling works with all other CL implementations I've tried. Is it just a matter of the code size? Thanks, Andrew

3 3

Problem - can't set environment variables when starting ABCL via Slime
by Andrew Sengul 21 Nov '21

21 Nov '21

Hello, I'm using ABCL through Emacs with Slime and I'm having trouble setting bash environment variables needed for Maven to work. Here's what I have in my ~/.emacs file: (setq slime-lisp-implementations '((abcl ("/usr/bin/java" "-jar" "/path/to/abcl-bin-1.8.0/abcl.jar" "/path/to/abcl-bin-1.8.0/abcl-contrib.jar" "-Xmx6g") :coding-system utf-8-unix :env ("JAVA_HOME=/path/to/jdk-12/" "PATH=/opt/apache-maven-3.8.3/bin:$PATH")))) Problem is, the $JAVA_HOME and $PATH variables are not set for the ABCL process despite putting them here. The environment variables do work with other CL implementations. When I set them in SBCL, for example, I can run (uiop:run-program "echo $PATH" ...) and see the extension added to the path. This doesn't work in ABCL, and I need those extra environment variables set in order for Maven to work. Does anyone know a way to fix this? It works for other CLs, so I'm guessing something particular about ABCL is preventing the variables from being set. Thanks, Andrew

1 0

[CfP] 15th European Lisp Symposium, March 21-22 2022, Porto, Portugal
by Didier Verna 20 Oct '21

20 Oct '21

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 15th European Lisp Symposium Call for Papers March 21-22, 2022 FEUP, Porto, Portugal & Online In co-location with <Programming> http://www.european-lisp-symposium.org/2022 Sponsored by EPITA ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Important Dates ~~~~~~~~~~~~~~~ - Submission deadline: January 23, 2022 - Author notification: February 21, 2022 - Final papers due: March 7, 2022 - Symposium: March 21-22, 2022 Scope ~~~~~ The European Lisp Symposium is a premier forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp dialects, including Common Lisp, Scheme, Emacs Lisp, Clojure, Racket, ACL2, AutoLisp, ISLISP, Dylan, SKILL, Hy, Shen, Carp, Janet, uLisp, Picolisp, Gamelisp, TXR, and so on. We encourage everyone interested in Lisp to participate. The European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Language design and implementation - Language integration, inter-operation and deployment - Development methodologies, support and environments - Educational approaches and perspectives - Experience reports and case studies Technical Program ~~~~~~~~~~~~~~~~~ We invite submissions in the following forms: * Papers: Technical papers of up to 8 pages that describe original results or explain known ideas in new and elegant ways. * Demonstrations: Abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. * Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. All submissions should be formatted following the ACM SIGS guidelines and include ACM Computing Classification System 2012 concepts and terms. Submissions should be uploaded to Easy Chair, at the following http://www.easychair.org/conferences/?conf=els2021 Note: to help us with the review process please indicate the type of submission by entering either "paper", "demo", or "tutorial" in the Keywords field. Programme Chair ~~~~~~~~~~~~~~~ Jim Newton - EPITA Research Lab (LRDE), France Programme Committee ~~~~~~~~~~~~~~~~~~~ tba -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

Error building 'babel' on ABCL 1.8.0 on Windows 10
by mortemeur 16 Sep '21

16 Sep '21

First of all, I assume this is my fault, but I do not know what I screwed up. I am sure I am accidentally leaving out important information, but if you ask me for it I would be happy to include it in a reply. I am trying to learn about Common Lisp and decided to use ABCL on Windows 10, I ran into this error while going through Xach's tutorial ( https://xach.livejournal.com/278047.html). Specifically, I ran: (quickproject:make-project "~/src/lisp/swatchblade/" :depends-on '(vecto hunchentoot)) The error I received is: Error while trying to load definition for system jna from pathname jar:file:///C:/abcl/abcl-contrib.jar!/mvn/jna.asd: Java exception 'java.lang.reflect.InaccessibleObjectException: Unable to make public java.lang.String java.util.jar.JarFile$JarFileEntry.getName() accessible: module java.base does not "opens java.util.jar" to unnamed module @6baeb178'. [Condition of type ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR] Restarts: 0: [TRY-RECOMPILING] Recompile invoke and try loading it again 1: [RETRY] Retry loading FASL for #<ASDF/LISP-ACTION:CL-SOURCE-FILE "jss" "base" "invoke">. 2: [ACCEPT] Continue, treating loading FASL for #<ASDF/LISP-ACTION:CL-SOURCE-FILE "jss" "base" "invoke"> as having been successful. 3: [RETRY] Retry #<ASDF/FIND-SYSTEM:DEFINE-OP > on #<ASDF/SYSTEM:UNDEFINED-SYSTEM "jna">. 4: [ACCEPT] Continue, treating #<ASDF/FIND-SYSTEM:DEFINE-OP > on #<ASDF/SYSTEM:UNDEFINED-SYSTEM "jna"> as having been successful. 5: [RETRY] Retry compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "cffi" "src" "cffi-abcl">. --more-- Backtrace: 0: (#<FUNCTION {16BC9E4C}> #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {73C52693}> #<FUNCTION {16BC9E4C}>) 1: (APPLY #<FUNCTION {16BC9E4C}> (#<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {73C52693}> #<FUNCTION {16BC9E4C}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {73C52693}> #<FUNCTION {16BC9E4C}>) 3: (INVOKE-DEBUGGER #<ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR {73C52693}>) 4: (ERROR ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR :NAME "jna" :PATHNAME #P"jar:file:///C:/abcl/abcl-contrib.jar!/mvn/jna.asd" ...) 5: (#<FUNCTION {34FA17C0}> #<JAVA-EXCEPTION {64C63DA9}>) 6: (SIGNAL #<JAVA-EXCEPTION {64C63DA9}>) 7: org.armedbear.lisp.Lisp.error(Lisp.java:382) 8: org.armedbear.lisp.Java.jcall(Java.java:946) 9: org.armedbear.lisp.Java$pf_jcall.execute(Java.java:790) 10: org.armedbear.lisp.Primitive.execute(Primitive.java:135) 11: (JCALL #<java.lang.reflect.Method public void java.lang.reflect.Ac.... {4EBBA1A7}> #<java.lang.reflect.Method public java.lang.String java.uti.... {1410F75D}> #<java.lang.Boolean true {41EEBB03}>) 12: (JSS::INVOKE-FIND-METHOD "getName" #<java.util.jar.JarFile$JarFileEntry META-INF/ {254EE0E9}> NIL) 13: (JSS::GET-ALL-JAR-CLASSNAMES #P"c:/abcl/abcl.jar") 14: (JSS:JAR-IMPORT #P"c:/abcl/abcl.jar") 15: (JSS::DO-AUTO-IMPORTS) 16: (#<FUNCTION (LAMBDA ()) {36EBDB7E}>) 17: (FUNCALL #<FUNCTION (LAMBDA ()) {36EBDB7E}>) 18: (SYSTEM:INIT-FASL :VERSION 43) 19: (SYSTEM::%LOAD #P"C:/Users/morte/AppData/Local/cache/common-lisp/abcl-1.8.0-fasl43-win-x64/C/abcl/abcl-contrib.jar/jss/invoke.abcl" NIL NIL T :DEFAULT) --more--

1 1

Issue running minimal example with jss: module java.base does not "opens java.util.jar" to unnamed module
by Phil Eaton 03 Aug '21

03 Aug '21

Hey folks, I've got a minimal program I'm trying to run: (require 'abcl-contrib) (require 'jss) (setf jss:*muffle-warnings* nil) (add-to-classpath #P"~/.m2/repository/io/javalin/javalin/3.13.10/") (jss:jar-import "javalin-3.13.10.jar") (let* ((port 8080) (app (#"start" (#"create" 'Javalin) port))) (begin (#"get" app (lambda (ctx) (#"result" ctx "Hello World"))))) When I run it: abcl --batch --noinform --load main.lisp I get the following exception when requiring jss I think. jssASDF could not load because Java exception 'java.lang.reflect.InaccessibleObjectException: Unable to make public java.lang.String java.util.jar .JarFile$JarFileEntry.getName() accessible: module java.base does not "opens java.util.jar" to unnamed module @1ece4432'.. Error loading /home/phil/.cache/common-lisp/abcl-1.8.0-fasl43-linux-x64/home/phil/vendor/abcl-bin-1.8.0/abcl-contrib.jar/jss/invoke.abcl at line 17 3 (offset 14319) #<THREAD "interpreter" {14B117F6}>: Debugger invoked on condition of type JAVA-EXCEPTION Java exception 'java.lang.reflect.InaccessibleObjectException: Unable to make public java.lang.String java.util.jar.JarFile$JarFileEntry.getName( ) accessible: module java.base does not "opens java.util.jar" to unnamed module @1ece4432'. Any suggestions for getting this (require :jss) working? Thank you! Phil

1 0

ASDF 3.3.5 is released
by Robert Goldman 03 Jul '21

03 Jul '21

Please consider upgrading the version you are distributing with your implementation. Note that this is strictly a bug fix release so should not cause issues in upgrading. But "should" -- software is unpredictable. Announcement email follows. Best, R

1 0

jnew-runtime-class
by phiroc＠free.fr 08 Jun '21

08 Jun '21

Hello, can anyone provide an example of using jnew-runtime-class? Here's the definition I found in the documentation: (CLASS-NAME &REST ; ARGS ; &KEY ; (SUPERCLASS java.lang.Object) ; INTERFACES ; CONSTRUCTORS ; METHODS ; FIELDS ; (ACCESS-FLAGS '(PUBLIC)) ; ANNOTATIONS ; (CLASS-LOADER (MAKE-MEMORY-CLASS-LOADER))) Many thanks. Best regards, Philippe

1 0

Bug # 391
by Don Morrison 27 May '21

27 May '21

I don’t think I have the ability to comment on bugs in the issue tracker, or, if I do, I’ve not figured out how to do it. I hope sending mail to this list for the purpose is acceptable; apologies if not. I note that #391 was opened six years ago, but remains unfixed, and, apart from apparently being pushed off from release to release, seems not to have received any love for four years. I just wanted to add a note to it that it is still being encountered in the wild, and is, at least in one user’s case, causing some pain. File names containing asterisks may not be a good idea, but sometimes we have no control over the names of files we are given. It also means at least one (uiop:subdirectories), and probably many, UIOP functions sometimes fail in what can appear to be mysterious ways on ABCL, but not other implementations. Thanks! -- Don Morrison <dfm(a)ringing.org> “There have been many triumphs of justice which are mockeries of law.” — Thomas Hardy, /The Return of the Native/

1 0

← Newer
1
2
3
4
5
6
7
8
...
120
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel