Mark Evenson

Closing issue as ironclad-0.58 from Quicklisp 2023-02-15 compiles and passes its test suite without issue. No specific work was done on this problem as far as I know.

Potentially very useful, but since redefining structures is not allowed in ANSI, I think we should 1. Add `:structure-redefinition-possible` to `*features*` 2. Make this the non-default somehow My reasoning behind...

Thanks @alejandrozf! This will go in for abcl-1.9.1

@alanruttenberg It would be cool to have these in pull requests, but keep 'em coming! When one changes the pathname code, one really needs to check the ABCL-TEST and ANSI-TEST...

Working with abcl-1.9.2: ``` CL-USER(8): (jnew-runtime-class "org.example.Foo") # CL-USER(9): (describe *) # is an object of type JAVA-OBJECT. The wrapped Java object is an instance of java.lang.Class: "class org.example.Foo" CL-USER(10):...

Present in abcl-1.9.2 ``` CL-USER> (pathname-directory "./../lib/abcl-aio.jar") (:RELATIVE :UP "lib") CL-USER> (lisp-implementation-version) "1.9.3-dev" "OpenJDK_64-Bit_Server_VM-MacPorts-17.0.8+7" "aarch64-Mac_OS_X-13.5.1" CL-USER> ```

Indeed, we adopted @alanruttenberg's proposed fix in . Closing.

CL-ENVIRONMENTS seems to provide a portable implementation that seems to work on ABCL.

> We might be able to fix some of this by using native functions to access the internal state. I have some environment inspection code - not sure if it...

> Below is a function for the slime inspector so they can be inspected. This is already part of the currently shipping SLIME . I suspect that the ABCL-INTROSPECT changes...