Predicate to distinguish between functions implemented directly in Java vs. Lisp

[trittweiler]

For Slime, we need a predicate to distinguish between
functions implemented in Java, and functions compiled
from Lisp. The reason is because we use different
mechanism to get at the definition: for Java functions,
we'll use TAGS, whereas for Lisp functions we will
use source-location information stored by the ABCL
compiler.

Compiled Lisp functions also end up to be of type Primitive,
so just making the Primitive class available to Lisp
won't cut it.

[ehuelsmann]

Proposed solution: Add a CompiledPrimitive class;
add a function which returns T if the argument passed in is either of type CompiledClosure or CompiledPrimitive.

That should address this request.

[ehuelsmann]

(In [12587]) Fix #88: Add the thread name to the debugger-printed message and

bind a restart which allows gracefully exiting a thread.

[ehuelsmann]

That was ticket #86 being fixed. Reopening.

[Mark Evenson]

See SourceLocation for additional proposal on how to improve the source location information in ABCL.

[Mark Evenson]

Status of proposed implementation unclear; re-analyze with Tobias.

[ehuelsmann]

(In [12932]) Fix #88: "We need SYS:COMPILED-LISP-FUNCTION-P" to distinguish
Java-defined and Lisp-defined functions (for SLIME).