Custom Query (1030 matches)
Results (493 - 495 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #346 | fixed | REPORT-DEFERRED-WARNINGS | ||
| Description |
In the end of compilation of McCLIM I get the following: > Error: value "home:lisp;site;mcclim;graphics.lisp.newest" is not of the expected type LIST. > While executing: CCL::DEF-INFO.MACRO-P, in process listener(1). > Type :POP to abort, :R for a list of available restarts. > Type :? for other options. 1 > :B *(7F957DE11868) : 0 (DEF-INFO.MACRO-P #(NIL NIL "home:lisp;site;mcclim;graphics.lisp.newest" (CCL::MACRO))) 82 (7F957DE118C0) : 1 (REPORT-DEFERRED-WARNINGS) 1573 (7F957DE11940) : 2 (CALL-WITH-COMPILATION-UNIT #<COMPILED-LEXICAL-CLOSURE (:INTERNAL CCL::WITH-COMPILATION-UNIT-BODY ASDF:OPERATE) #x7F957F43543F> [...]) 245 |
|||
| #949 | fixed | RESTART-CASE with :TEST & :INTERACTIVE broken | ||
| Description |
There seems to be some odd behavior in RESTART-CASE when a restart clause has both test and interactive expressions. In the attached file, the only difference between TEST-BROKEN-RESTART and TEST-WORKING-RESTART is that the latter’s restart clause has no test expression. ./dx86cl64 --no-init Welcome to Clozure Common Lisp Version 1.9-dev-r15272M-trunk (DarwinX8664)! ? (load "~/broken-restart.lisp") #P"/Users/greg/broken-restart.lisp" This case behaves correctly – the test fails, so the restart is not offered. ? (test-broken-restart 'non-restartable-error) > Error: Condition #<NON-RESTARTABLE-ERROR #x30200072ED8D> 1 > :r > Type (:C <n>) to invoke one of the following restarts: 0. Return to break level 1. 1. #<RESTART ABORT-BREAK #x7EBECD> 2. Return to toplevel. 3. #<RESTART ABORT-BREAK #x7EC5AD> 4. Reset this thread 5. Kill this thread 1 > :pop This case fails – the test passes and the restart is offered, but when the restart is selected, rather than calling the interactive expression, some anonymous restart is used, and another error is signaled. ? (test-broken-restart 'restartable-error) > Error: Condition #<RESTARTABLE-ERROR #x302000726B1D> 1 > :r > Type (:C <n>) to invoke one of the following restarts: 2. #<RESTART BROKEN #x7EC16D> 1 > :c 2 Invoking restart: NIL 432345564230164480 is not of type (OR SYMBOL FUNCTION), and can't be FUNCALLed or APPLYed 1 > :pop This is the same as the previous case, but with the test expression removed. This time it works – the restart is selected, then it interactively asks for a value. ? (test-working-restart 'restartable-error) > Error: Condition #<RESTARTABLE-ERROR #x302000721A6D> 1 > :r > Type (:C <n>) to invoke one of the following restarts: 2. #<RESTART WORKING #x7EC16D> 1 > :c 2 Invoking restart: #<RESTART WORKING #x7EC16D> Enter a value: 5 5 ? |
|||
| #318 | fixed | RUN-PROGRAM I/O limitations | ||
| Description |
(run-program ''prog'' args :output ''lisp-stream'' :error ''lisp-stream'') doesn't work as expected. CCL::MONITOR-EXTERNAL-PROCESS only has the ability to watch output on a single file descriptor, and in this case it winds up watching the input side of a pipe used as the error descriptor by the external program, and output is lost. Example: (defun foo ()
(with-output-to-string (out)
(with-output-to-string (err)
(run-program "ls" '("-l") :output out :error err)
(format t "~& out = ~a" (get-output-stream-string out))
(format t "~& err = ~a" (get-output-stream-string err))))
nil)
Calling (FOO) produces the output: out = err = which basically means "there was no error output, and we weren't watching standard output" Even though this is apparently a litte obscure (I don't recall it ever having been reported), it's probably fair to call it 'major'. Using :ERROR :OUTPUT provides a way of getting both standard and error output, but not a way of distinguishing between them. |
|||
