Custom Query (1030 matches)

Sometimes the compiler warns

style-warning: Unused lexical variable FOO

where FOO is some variable I've SETQ'd but then not referred to.

That's annoying enough. I don't think that should be done at all. It's a pain to have to throw away documentary (multiple-value-setq (x y z) ...) variables or go through other hoops just to get rid of this warning. Also, it's "used" by reasonable definition: it's set, just not "read" or "eval'd". Whatever. It's a pain to encounter and to work around.

But that's not the main point.

Sometimes -- not always!! -- I cannot even still the compiler by simply placing the variable inline to be evaluated.

The compiler first of all is so clever as to optimize out the reference, then turns on me and tells me it's not referenced. That is quite frustrating to put it mildly.

Seems to happen in big functions. Small functions work fine, so I cannot give you an example. But it's like this:

  (defun foo (a b) 
       (let (c d)
         (multiple-value-setq (c d) (round a b))
         c))

always warns about D "unused" (annoying to me, but I can deal with it)

  (defun foo (a b) 
       (let (c d)
         (multiple-value-setq (c d) (round a b))
         d
         c))

not in this case, but in some larger functions, warns about D -- unacceptable, bug, etc.!

Note: let me know if this is a known problem: that is, the flakyness (dependency on function size, or whatever), or -- if not -- if you need an example. I'll put cycles on it, but would rather not if it's already known.

Version info:

            CCL::*OPENMCL-MAJOR-VERSION*,  Value: 1
            CCL::*OPENMCL-MINOR-VERSION*,  Value: 6

I have run into this kind of problem many times with my EasyGui efforts, and thought it must be my own fault. But now I've come across it using the Search Files dialog, which is nothing to do with me. This kind of thing pops up in the AltConsole window:

Error: Array index 5 out of bounds for #<SLOT-VECTOR [CCL::SLOT-VECTOR ==> CCL::GVECTOR ==> T] #x136DC716> .

While executing: (:INTERNAL GUI::doSearch:|), in process Initial(0).

Type :POP to abort, :R for a list of available restarts. Type :? for other options.

1 >

It is not reliably repeatable.

fwiw, I have suspected that it is due to some race condition whereby instances of Cocoa subclasses get information enough added to them for some objc method to be dispatched, but the extra Lisp slots appropriate for the class have not yet been added. This is just a hunch, maybe helpful and maybe way off the mark.

MCL does this. useful. Sometimes I like to have many inspector windows opened automatically during debugging. I want to close the inspector windows then with a single option-click into the close box.