Custom Query (1030 matches)
Results (658 - 660 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #295 | fixed | Spurious warning at high safety | ||
| 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 | ||
| Description |
On Sun, May 18, 2008 at 1:00 AM, Gary Byers <gb@…> wrote: '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.) |
|||
| #311 | fixed | can't execute-selection that ends in a comment | ||
| Description |
From openmcl-devel: At 6/10/2008 01:54 AM, Rich Sutton wrote: in the ide, bring up a listener. then make a buffer that ends with a comment, say a new buffer with just a ; in it. finally, select the contents of the buffer and invoke execute-selection. your listener will disappear. otherwise appears to be harmless. applies to multi-line comments too -- i ran into this because i had a bunch of test code commented out at the end of some file i was working on. |
|||
