From: SourceForge.net <no...@so...> - 2005-03-30 13:15:57
|
Bugs item #1103722, was opened at 2005-01-17 10:19 Message generated for change (Comment added) made by demoss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=1103722&group_id=4933 Category: Lisp Core Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert Dodier (robert_dodier) Assigned to: Nobody/Anonymous (nobody) Summary: compile_file claims compilation failed when it succeeded Initial Comment: compile_file uses the tertiary return value of COMPILE-FILE to tell whether the compilation succeeded. At least one lisp (Clisp) returns a positive value if there are warnings, so compile_file thinks the compilation failed when actually there weren't errors. A comment in the code (src/transs.lisp) says ;; If the compiler encountered errors, don't set bin-file to ;; indicate that we found errors. Is this what we want? I think the answer is "no". ---------------------------------------------------------------------- Comment By: Nikodemus Siivola (demoss) Date: 2005-03-30 16:15 Message: Logged In: YES user_id=283348 The third return value of COMPILE-FILE indicates presence of errors or non-style-warning warnings; non-style-warning warnings are an indication of real problems and undefined behaviour, and should be treated as such: eg. SBCL emits full warnings for unbound variables and type-errors detected at compile-time. In other words, the current behaviour is IMO good and safe. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=1103722&group_id=4933 |
From: SourceForge.net <no...@so...> - 2006-04-10 18:47:54
|
Bugs item #1103722, was opened at 2005-01-17 01:19 Message generated for change (Settings changed) made by robert_dodier You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=1103722&group_id=4933 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Lisp Core - Translator Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert Dodier (robert_dodier) Assigned to: Nobody/Anonymous (nobody) Summary: compile_file claims compilation failed when it succeeded Initial Comment: compile_file uses the tertiary return value of COMPILE-FILE to tell whether the compilation succeeded. At least one lisp (Clisp) returns a positive value if there are warnings, so compile_file thinks the compilation failed when actually there weren't errors. A comment in the code (src/transs.lisp) says ;; If the compiler encountered errors, don't set bin-file to ;; indicate that we found errors. Is this what we want? I think the answer is "no". ---------------------------------------------------------------------- Comment By: Nikodemus Siivola (demoss) Date: 2005-03-30 06:15 Message: Logged In: YES user_id=283348 The third return value of COMPILE-FILE indicates presence of errors or non-style-warning warnings; non-style-warning warnings are an indication of real problems and undefined behaviour, and should be treated as such: eg. SBCL emits full warnings for unbound variables and type-errors detected at compile-time. In other words, the current behaviour is IMO good and safe. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104933&aid=1103722&group_id=4933 |