Custom Query (1030 matches)

When building a standalone binary using SAVE-APPLICATION and :PREPEND-KERNEL T, I found the command line argument processing of the resulting binary undesirable. I have a patch that solves the problem for me, however, it might not be the best way of doing things.

The problem as I see it is as follows: When only one argument (which does not begin with a '-') is provided to a binary which consists of (kernel + heap-image), the current kernel code automatically tries to load that argument as the image even though it should clearly use the image attached to the binary itself. As a result, one has to always use the '--' argument to end processing of the kernel arguments. This behavior is not expected for unix command line tools and shouldn't be expected here either IMHO.

The attached patch provides a sub-optimal solution which basically detects the case when the heap image is already included in the binary and so does not try to load the image from that first argument. The problem with this is that since '--' is not required, other kernel level command line flags, such as -I, -R, -S, etc, that are not passed on to the application may cause some confusion.

Another solution is to completely disable those kernel level flags if the heap image is attached to the kernel, but the loss of control over those parameters is also undesirable.

OpenMCL ships with a bunch of useful functionality relegated to the 'Examples' directory. This stuff includes the nascent Hemlock editor, various support classes, and other tools that I have found useful trying to port the "Open Agent Engine" to OpenMCL.

Can these useful things be moved to a more permanent location, perhaps as a "Cocoa" library or something along those lines?

Ideally, the cocoa support stuff would be its own library, with perhaps GTK/GNUstep as alternative implementations of the same ideas.

Backup files in Cocoa have names of the form "foo~.lisp". Whatever advantage this may have over the Emacs convention (backup files have the same extension as the original) seems to be outweighed by the disadvantage (backup files have the same extension as the original), so things like "grep FOO *.lisp" require extra effort and things like filename completion get unnecessarily confused.

I don't know how to influence the naming convention, but we can probably bypass the automatic mechanism and figure out how to rename the original file (when applicable) just before saving. (There may be issues with preserving Finder aliases and such unless this is done carefully, but I assume that it's doable.)

(In short, I vote for "foo.lisp~" ...)