Custom Query (1030 matches)

If the CCL IDE bundle is moved out of the CCL directory and executed, certain functions will fail (e.g. just do #&NSApp in the listener and see what happens). This is because the ccl: logical translation no longer points to the CCL directory, but rather to whatever directory the bundle is in. This is set by the init-ccl-directory-for-ide function. This could also be a problem for any saved applications depending on what they do. There are various ways this could be addressed: 1) add a new value into the Info.plist identifying the CCL directory and use it to initialize the ccl: translation 2) Modify init-ccl-directory-for-ide to search for the right directory 3) create a physical link to the CCL directory in the bundle somewhere and use that as the translation for the ccl: logical directory, 4) add a user preference that identifies where the CCL directory is and use that to initialize the translation. I prefer #4 because it is easier to change if the bundle is moved to a different machine or if the CCL directory is moved at some point. #2 is intriguing but depending on how the search is done, could take a significant amount of time. So I am requesting an enhancement to the IDE that adds a preference item identifying the CCL directory. It should default to the value currently used. In the meantime I will assure that applications that my tools generate will reset the logical translation in some way.

SBCL has a sb-debug::backtrace-as-list function which returns the backtrace summary in list form. This is useful for certain kinds of tracing and profiling. The attached diff adds a similar function to OpenMCL/CCL.

From IRC:

<eslick> Is there a known version of slime that works with ccl 1.3? the latest fails with Condition: Module XREF was not provided by any function on *MODULE-PROVIDER-FUNCTIONS*.