[Openmcl-devel] [Newbie] Cocoa Listener Up, But No Cocoa Inspector
helink at sandia.gov
Tue May 20 18:41:43 EDT 2003
My bad, cinspect isn't exported from ccl or imported into cl-user (the
namespace that the read-eval-print loop starts in). You should
entertain better luck with
Since you're claiming newbiness, I should add that
-- ccl is the package identifier for the namespace the cocoa inspector
(and a lot of other stuff) is defined in
-- the colon ":" or (in this case) double-colon "::" is how a symbol in
another package than the current one is referred to. Single colons only
let you refer to exported symbols of a package, double-colon lets you
refer to non-exported symbols of a package (in general, DON'T USE
double-colon, it's dangerous -- in this case it's OK because it's an
error that cinspect isn't exported, and even then it would be better to
fix that problem, which I think I'll go do right now but that won't
help you so just use ::)
On Tuesday, May 20, 2003, at 03:43 PM, Dave Newman wrote:
> I restarted mcl from a command line and evaluated (require
> "COCOA-INSPECTOR"). This brought up the Cocoa listener and no errors
> or warnings were reported in either the Cocoa listener, or in the
> terminal based mcl listener.
> Evaluating (cinspect 1) results in:
>> Error in process Listener(3): Undefined function CINSPECT called with
>> arguments (1) .
>> While executing: "Unknown"
>> Type :GO to continue, :POP to abort.
>> If continued: Retry applying CINSPECT to (1).
> Type :? for other options.
> I don't know what I'm doing wrong at this point. Any help would be
> --Dave Newman
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
Openmcl-devel mailing list
Openmcl-devel at clozure.com
More information about the Openmcl-devel