Custom Query (1030 matches)

The manual doesn't say it does, but native-translated-namestring merges its argument with *default-pathname-defaults*, which does nothing when the default value of #p"" is used, but can yield interesting results in other cases. This behavior is not mentioned in the manual: ​http://ccl.clozure.com/manual/chapter4.6.html

Personally, I'd consider that a bug, for merging is not what I'd expect from this function. However, maybe you have a different idea and this behavior is what you desire - in which case I consider that a bug in the documentation, for that is very surprising (to me at least).

My workaround is to bind *default-pathname-defaults* to #p"" around my call to native-translated-namestring.

At times, our application QRes has the following error message:

There is no applicable method for the generic function:

<Compiled-function CCL::%%ONE-ARG-DCODE #x3000002039CF>

when called with arguments:

(NIL)

The backtrace subsequently reveals that there was an actual bug in our application relating to a calling a one-argument generic function with an invalid value. However, the name of said generic function was lost in this error message.

Can CCL somehow improve its error message by revealing the name of the user function that got optimized into a CCL::%%ONE-ARG-DCODE ?

Xref: ITA bug 113986 Xref: ITA bug 105855

I haven't been able to reduce that to a small runnable example yet, but when we compile our application with (ccl::snap-reader-methods :known-sealed-world t)

If we subsequently re-define a class, even identically, some existing methods using that class will fail with an "Invalid memory operation". That's with 1.8-r15359 LinuxX8664. Before the patch from http://trac.clozure.com/ccl/changeset/14968 was used, it was a plain crash.

Can CCL be patched so that any class-redefinition after snap-reader-methods would invalidate the snapped reader methods, and possibly issue a warning or continuable error (since a promise was broken)?

Xref: ITA bug 105557