January 2013 - cmucl-imp - mailman3.common-lisp.net

[cmucl-imp] Please kill those notes
by Faré 29 Jan '13

29 Jan '13

Why do these output a compilation note about some unused macroexpanded case? How do I muffle the notes? (defmethod print-object ((o operation) stream) (print-unreadable-object (o stream :type t :identity nil) (ignore-errors (format stream "~{~S~^ ~}" (operation-original-initargs o))))) (defmethod perform-with-restarts ((o load-op) (c cl-source-file)) (loop (restart-case (return (call-next-method)) (try-recompiling () :report (lambda (s) (format s "Recompile ~a and try loading it again" (component-name c))) (perform (find-operation o 'compile-op) c))))) —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org *EULA: By reading or responding to this message you agree that all my stated or unstated opinions are correct.* "EULA" — patent pending.

2 5

[cmucl-imp] ASDF support for deferred warnings in CMUCL?
by Faré 26 Jan '13

26 Jan '13

Dear CMUCL developers, I've been adding support for ASDF to save deferred warnings (typically, forward function references) in a file, so that if you do an incremental compilation, warnings from previously compiled files are still correctly handled at the end of the virtual with-compilation-unit. I've added support for SBCL and CCL myself, which was made much easier by being able to read the source code to their compilers, but I don't feel like groveling through four more free sofware compilers. Would you be interested in implementing the same feature for CMUCL, or at least in guiding me on how to do so? The code is mainly in asdf/lisp-build.lisp functions reify-deferred-warnings unreify-deferred-warnings reset-deferred-warnings. http://common-lisp.net/gitweb?p=projects/asdf/asdf.git Best regards, —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Better, faster, cheaper — pick any two.

2 1

Re: [cmucl-imp] Upgrade issues
by Faré 22 Jan '13

22 Jan '13

CMUCL is one of the three implementations, together with ABCL and CLISP, where I ultimately punted on ASDF hot-upgrade, by just trying to rename away the ASDF package if it's too old. My package surgery looks like it works, but it looks like CMUCL refuses to invalidate old CLOS methods when I fmakunbound an object, and/or refuses to invalidate them in some caches. Therefore, the old methods keep getting called and the upgrade fails in weird ways. Trying to unintern the symbols for individual offending functions doesn't work either; I don't remember the symptoms. It's too late to fix the old ASDF so it is easier to upgrade, but maybe there are declarations I can put in the current ASDF to prevent some of these "optimizations" to be in place? If you're interested in fixing this kind of issues, I can try to come up with reduced examples. Anyway, please test the latest ASDF with CMUCL, I think it's ripe for release, except for those upgrade woes. I'd like your feedback considering the massive amount of hacking that happened. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Antivirus alert: file .signature infected by signature virus. Hi! I'm a signature virus. Copy me into your sig file and help me spread!

2 1

[cmucl-imp] Happy New Year with snapshot-2013-01
by Raymond Toy 02 Jan '13

02 Jan '13

Happy New Year! Yet another month and year has passed and so we have the first snapshot of 2013. Binaries will be uploaded soon. Some notable changes: Fixed tickets: Ticket 66: replace on simple strings Ticket 67: deftransform for replace is unsafe Ticket 68: bit-bash-copy can't handle very large objects. :ALIEN-CALLBACK added to *FEATURES* for platforms (x86, sparc, ppc) that support alien callbacks. Ray

1 1