Custom Query (1030 matches)

I was surprised that ccl:save-application called ccl:*lisp-cleanup-functions* before saving the image. I expected a snapshot of the current image (this is the behavior of other implementations), not an image in a post-shutdown state.

I can use ccl:*save-exit-functions* to save the desired state, or restore state with ccl:*lisp-startup-functions*, but neither may be easy in general.

If it is decided that the current behavior is preferred, then at least document it in ccl:save-application or elsewhere, as it differs from other implementations.

From: Joakim Sandgren <joakim@…>
Date: April 4, 2009 5:04:22 PM EDT
To: openmcl-devel@…
Subject: [Openmcl-devel] menu

And one more,
Would it be very difficult to add the functionality to choose a file that you will load, instead of having to open it to be able to load it?

Thank you.

Joakim

According to CLHS entry for Constant Variable LAMBDA-LIST-KEYWORDS, it is "a list of all the lambda list keywords used in the implementation, including the additional ones used only by macro definition forms".

(arglist #'+) on CCL returns (CCL::&LEXPR CCL::NUMBERS), which includes a keyword &LEXPR that is not on the LAMBDA-LIST-KEYWORDS list.

Therefore I conclude that CCL is not compliant when it comes to this issue.

This is a suggested patch to fix this behaviour.

​https://github.com/phoe/ccl/commit/5ac9d024c08fc5eb5302491be218143640aa3388