Custom Query (1030 matches)
Results (403 - 405 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #290 | fixed | THE typechecking and evaluation order | ||
| Description |
This should already be fixed in r9331, but for the record and in case it rears its ugly head again. The TYPED-FORM acode operation (basically, the acode representation of THE) now takes an extra argument indicating whether or not a runtime typecheck should occur; this is set to T by the frontend at high SAFETY levels. Historically, a TYPED-FORM acode operation was considered "simple and side-effect free" if its operand was and could therefore be evaluated out-of-order, but this is no longer true if typehecking is involved. (Since that typechecking can involve function calls and a lot of register shuffling, a typechecking TYPED-FORM should be viewed as something that has unknown side-effects and which can at least change register contents.) |
|||
| #292 | fixed | Console window should not become the front window whenever a new message appears | ||
| Description |
The new console window in v1.2 becomes the front window whenever a new message appears. This is annoying, particularly when e.g. exiting a break loop using cmd-. because that causes an exitBreak message to appear (and hence removes focus from the listener). |
|||
| #293 | fixed | ADVISE makes functions cons | ||
| Description |
When a function is advised, it conses a small amount of memory every time it is called. It seems as if ADVISE-GLOBAL-DEF is at fault. It would be better if the encapsulation for the function would not allocate memory, i.e. to reduce overhead when profiling inner loops. |
|||
