Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (400 - 402 of 1030)

Ticket Resolution Summary Owner Reporter
#287 fixed Can't trace single-method generic functions gz gz
Description
? (defmethod frotz (x) (print x))
#<STANDARD-METHOD FROTZ (T)>
? (trace frotz)
NIL
? (frotz 17)
0> Calling (FROTZ 17) 
> Error: Too many arguments in call to #<METHOD-FUNCTION FROTZ (T)>:
>        2 arguments provided, at most 1 accepted. 
> While executing: #<STANDARD-METHOD FROTZ (T)>, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options.
1 > 
#295 fixed Spurious warning at high safety gz gz
Description

Compiling a file containing:

(defun outer-fun ()
  (defun inner-fun () nil)
  (inner-fun))

gives a warning (undefined function inner-fun) when compiled with (optimize (safety 3)) but not otherwise.

#301 fixed console log window needs to be less intrusive gz gz
Description

On Sun, May 18, 2008 at 1:00 AM, Gary Byers <gb@…> wrote:
Sometimes when running the Cocoa IDE, people have reported seeing messages like:

'SystemFlippers: didn't consume all data for xmnu ..."

or something similar appear in the console window. Andrew said that he saw this when double-clicking on a lisp file to start the IDE.

AFAIK (er, "according to Google searches") this has something to do with Apple code not handling endianness of (classic Macos-style) resource IDs in some cases. AFAIK, these messages are harmless and uninteresting. I don't know how to tell in the general case whether a message like this is interesting; seeing meaningless gibberish like this presented as if it was something that the user would and should care about doesn't create a good impression; not calling the user's attention to something that's actually important isn't ideal either.

It's probably closer to the right thing to give some indication that there's some sort of diagnostic output available and not automatically pop up the console window when that output first appears. Whatever that indication is it should somehow be visible without being intrusive.

(I think that there are some leftover calls to NSLog in the IDE itself.)

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.