Skip to content
Snippets Groups Projects
Commit b60ec699 authored by Robert P. Goldman's avatar Robert P. Goldman
Browse files
parents 58dfd53f e94b2dfb
No related branches found
No related tags found
No related merge requests found
...@@ -103,63 +103,75 @@ ...@@ -103,63 +103,75 @@
make t l=cmucl t=test-encodings.script make t l=cmucl t=test-encodings.script
which was a different PCL bug from the above (without same workaround) which was a different PCL bug from the above (without same workaround)
but possibly also triggered by the non-standard declaim. but possibly also triggered by the non-standard declaim.
*** `#5(1 ,@`(2 3)))` returns #(1 2 3),
rather than #(1 2 3 2 3 2 3 2 3) or even better #(1 2 3 3 3).
** XCL has bad bugs: ** XCL has bad bugs:
make-pathname doesn't handle :type nil properly and *** make-pathname doesn't handle :type nil properly and
has massive lossage in logical-pathname support. has massive lossage in logical-pathname support.
If using block () and return in search-for-system-definition *** If using block () and return in search-for-system-definition
instead of return-from, XCL mistakenly has the return jump instead of return-from, XCL mistakenly has the return jump
to the end of the try function or something. to the end of the try function or something.
It also takes a long time for errors to propagate into a debugging REPL — *** It also takes a long time for errors to propagate into a debugging REPL —
Maybe O(n^3) behavior or worse in walking the C++ stack? Maybe O(n^3) behavior or worse in walking the C++ stack?
The backtrace frames may contains unprintable objects. *** The backtrace frames may contains unprintable objects.
make-pathname fails to copy the version from the defaults. *** make-pathname fails to copy the version from the defaults.
(make-pathname :host "ASDFTEST" :directory '(:absolute "system2" "module4") *** (make-pathname :host "ASDFTEST" :directory '(:absolute "system2" "module4")
:name nil :type nil) fails to handle the logical-pathname-ness of ASDFTEST. :name nil :type nil) fails to handle the logical-pathname-ness of ASDFTEST.
*** `#5(1 ,@`(2 3)))` returns #(1 2 3),
rather than #(1 2 3 2 3 2 3 2 3) or even better #(1 2 3 3 3).
** GCL is almost working again; but implementation bugs remain. ** GCL is almost working again; but implementation bugs remain.
See November 2013 discussion on gcl-devel. See November 2013 discussion on gcl-devel.
* Another GCL compiler bug: *** Another GCL compiler bug:
when I changed the definition of getcwd from when I changed the definition of getcwd from
(let ((*default-pathname-defaults* #p"")) (truename #p"")) to (let ((*default-pathname-defaults* #p"")) (truename #p"")) to
(let ((*default-pathname-defaults* *nil-pathname*)) (truename *nil-pathname*)) (let ((*default-pathname-defaults* *nil-pathname*)) (truename *nil-pathname*))
to guard against e.g. a logical-pathname context while loading asdf to guard against e.g. a logical-pathname context while loading asdf
and parsing #p"", calls to getcwd result in a segfault. and parsing #p"", calls to getcwd result in a segfault.
* An another bug: gcl refuses dynamic-extent declaration on functions. *** An another bug: gcl refuses dynamic-extent declaration on functions.
uiop/stream.lisp: #-gcl (declare (dynamic-extent ,@(when uiop/stream.lisp: #-gcl (declare (dynamic-extent ,@(when
before `(#',beforef)) ,@(when after `(#',afterf)))) before `(#',beforef)) ,@(when after `(#',afterf))))
* (typep p 'logical-pathname) should be T if p has a logical-pathname host. *** (typep p 'logical-pathname) should be T if p has a logical-pathname host.
* apropos is case-sensitive and returns a same symbol many times *** apropos is case-sensitive and returns a same symbol many times
* compile-file fails to return proper secondary values in case of non-style WARNING. *** compile-file fails to return proper secondary values in case of non-style WARNING.
* (pathname-directory #p"foo/") is incorrectly ("foo") instead of (:RELATIVE "foo") *** (pathname-directory #p"foo/") is incorrectly ("foo") instead of (:RELATIVE "foo")
* Missing: chdir, combine-fasls, and plenty more UIOP functions. *** Missing: chdir, combine-fasls, and plenty more UIOP functions.
* Do whatever it takes to pass the asdf tests, add the above? *** Do whatever it takes to pass the asdf tests, add the above?
* Have (require "asdf") and (require "ASDF") both work. *** Have (require "asdf") and (require "ASDF") both work.
* Trying to uiop:slurp-stream-forms from a stream with #+(or) :foo *** Trying to uiop:slurp-stream-forms from a stream with #+(or) :foo
(or read-file-forms from an file with same) results in an error, (or read-file-forms from an file with same) results in an error,
rather than nil. This is probably a bug in #+ processing. rather than nil. This is probably a bug in #+ processing.
Unhappily, debian creates such a file in Unhappily, debian creates such a file in
/etc/common-lisp/asdf-output-translations.conf.d/01-common-lisp-controller.conf /etc/common-lisp/asdf-output-translations.conf.d/01-common-lisp-controller.conf
* Tests that try to catch an error fail (but catching a warning succeeds), *** Tests that try to catch an error fail (but catching a warning succeeds),
which suggests brokenness in handler-bind and/or error. which suggests brokenness in handler-bind and/or error.
*** `#5(1 ,@`(2 3)))` returns #(1 2 3),
rather than #(1 2 3 2 3 2 3 2 3) or even better #(1 2 3 3 3).
** Find out why ABCL fails the timestamp propagation test. ** ABCL has a few bugs.
*** ABCL fails the timestamp propagation test.
*** `#5(1 ,@`(2 3)))` returns #(1 2 3),
rather than #(1 2 3 2 3 2 3 2 3) or even better #(1 2 3 3 3).
** ECL has issues with its bundles. ** ECL has issues with its bundles.
On MacOS X, test-bundle.script fails. On MacOS X, test-bundle.script fails.
On Linux, test-program.script fails with recent ECL 237af2e, On Linux, test-program.script fails with recent ECL 237af2e,
but used to work quite fine earlier in 2013. but used to work quite fine earlier in 2013.
* Find an easier way to bind variables around compilation and loading of files
* Design & Implement some out-of-line configuration mechanism for various options? * Design & Implement some out-of-line configuration mechanism for various options?
i.e. let configuration files override some variables around some actions. i.e. let configuration files override some variables around some actions.
* Could be used to override new backward-incompatible defaults ** Could be used to override new backward-incompatible defaults
(e.g. for operation propagation, deferred warnings, etc.) (e.g. for operation propagation, deferred warnings, etc.)
* Use the above variable binding mechanism. ** Use the above to bind variable around performing of actions.
* Fix bugs on http://bugs.launchpad.net/asdf/+bugs * Improve robustness
** fix directory-files to not return directories on CCL, etc. Add tests. ** Fix bugs on http://bugs.launchpad.net/asdf/+bugs
*** fix directory-files to not return directories on CCL, etc. Add tests.
*** have a better defsystem form verifier - see lp#1007335
*** have a function verify-strict-asd that can verify a asd is pure lp#541562
Then if it passes, use load-strict-asd.
If not, optionally issue a warning. Start migrating people toward that.
* Learn to use cl-grid-test * Learn to use cl-grid-test
** So we can easily make sure ASDF changes don't break stuff, ** So we can easily make sure ASDF changes don't break stuff,
...@@ -173,12 +185,6 @@ ...@@ -173,12 +185,6 @@
* have a mode to explain WHY a component needs to be recompiled. * have a mode to explain WHY a component needs to be recompiled.
* Improve robustness
** have a better defsystem form verifier - see lp#1007335
** have a function verify-strict-asd that can verify a asd is pure lp#541562
Then if it passes, use load-strict-asd.
If not, optionally issue a warning. Start migrating people toward that.
* have with-input-file use the encodings mechanism? * have with-input-file use the encodings mechanism?
** Import asdf-encodings into UIOP? Sounds a lot of code for no users. ** Import asdf-encodings into UIOP? Sounds a lot of code for no users.
...@@ -191,8 +197,7 @@ ...@@ -191,8 +197,7 @@
* Include some ABL test for stassats's (now obsolete?) thing: * Include some ABL test for stassats's (now obsolete?) thing:
(asdf:enable-asdf-binary-locations-compatibility (asdf:enable-asdf-binary-locations-compatibility
:centralize-lisp-binaries t :default-toplevel-directory :centralize-lisp-binaries t :default-toplevel-directory *fasl-dir*)
*fasl-dir*)
** Or deprecate and remove ABL compatibility altogether? ** Or deprecate and remove ABL compatibility altogether?
No one has been using ASDF1 for years. No one has been using ASDF1 for years.
There is no ABL to be compatible with — There is no ABL to be compatible with —
...@@ -252,7 +257,7 @@ It looks like SWANK can be fixed soon, though, so we'll see. ...@@ -252,7 +257,7 @@ It looks like SWANK can be fixed soon, though, so we'll see.
*** cl-irc cliki-bot rss cl-syslog com.informatimago.clext *** cl-irc cliki-bot rss cl-syslog com.informatimago.clext
com.informatimago.clisp com.informatimago.clmisc com.informatimago.clisp com.informatimago.clmisc
com.informatimago.common-lisp.arithmetic com.informatimago.common-lisp.arithmetic
om.informatimago.common-lisp.bank com.informatimago.common-lisp.bank
com.informatimago.common-lisp.cesarum com.informatimago.common-lisp.cesarum
com.informatimago.common-lisp com.informatimago.common-lisp.csv com.informatimago.common-lisp com.informatimago.common-lisp.csv
com.informatimago.common-lisp.cxx com.informatimago.common-lisp.cxx
...@@ -321,10 +326,23 @@ It looks like SWANK can be fixed soon, though, so we'll see. ...@@ -321,10 +326,23 @@ It looks like SWANK can be fixed soon, though, so we'll see.
* See message from 2014-01-27 05:26:44 GMT for stuff to document. * See message from 2014-01-27 05:26:44 GMT for stuff to document.
http://thread.gmane.org/gmane.lisp.asdf.devel/3675/focus=3695 http://thread.gmane.org/gmane.lisp.asdf.devel/3675/focus=3695
* deferred-warnings support probably needs to be redone better. * UIOP
* implement deferred warnings support on lispworks ** deferred-warnings support probably needs to be redone better.
* turn undefined function style-warnings into full warnings(?) *** implement deferred warnings support on lispworks
* work with cl-test-grid to eliminate deferred warnings from quicklisp libraries *** turn undefined function style-warnings into full warnings(?)
* https://www.mail-archive.com/asdf-devel@common-lisp.net/msg03608.html *** work with cl-test-grid to eliminate deferred warnings from quicklisp libraries
* czak@google.com rewrote part of deferred warnings support. *** https://www.mail-archive.com/asdf-devel@common-lisp.net/msg03608.html
*** czak@google.com rewrote part of deferred warnings support.
Ask him for the code he implemented at Google. Ask him for the code he implemented at Google.
** define-package cannot deal with symbols moving "forward".
*** document that THOU SHALT NOT USE :RECYCLE with packages previously
defined by define-package when building from scratch.
*** Maybe add a check? But how to tell whether you're building from scratch?
*** Add some :moved-to directive to define-package, such that
(:moved-to forward-package symbols...)
will declare symbols as moved forward: when the symbol already exists,
it is moved to the forward package if that package already exists,
after the package created if it doesn't exist yet (!)
*** There again, a check that a forward-package is not backward
would be very nice.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment