Re: [asdf-devel] PERFORM COMPILE-OP diagnostics

2010-01-04 Thread Christophe Rhodes
"Tobias C. Rittweiler" writes: >> In particular, I think that your characterization of failurep from >> compile-file being treated as a failure as "obtusive" is not helpful. > > My posting refered to the _diagnostics_ that is output, and not to the > aborting behaviour. > > What information do yo

Re: [asdf-devel] PERFORM COMPILE-OP diagnostics

2010-01-04 Thread Tobias C. Rittweiler
Christophe Rhodes writes: > "Tobias C. Rittweiler" writes: > > > I don't like that behaviour at all for the following reasons: > > I do. (Not that I have a vote, but I think there is some value in > binary tools, which fail hard when things go wrong). Also possibly > relevant is the fact that s

Re: [asdf-devel] PERFORM COMPILE-OP diagnostics

2010-01-04 Thread Christophe Rhodes
"Tobias C. Rittweiler" writes: > I don't like that behaviour at all for the following reasons: I do. (Not that I have a vote, but I think there is some value in binary tools, which fail hard when things go wrong). Also possibly relevant is the fact that some of my systems use the current inter

[asdf-devel] PERFORM COMPILE-OP diagnostics

2010-01-04 Thread Tobias C. Rittweiler
The code in question is (multiple-value-bind (output warnings-p failure-p) (apply #'compile-file source-file :output-file output-file (compile-op-flags operation)) (when warnings-p (case (operation-on-warnings operation) (:warn (warn "~@"