TODO 14.5 KB
Newer Older
1 2
* Decree that versions older than 2 years are not supported;
  yet, keep supporting an upgrade from whatever vendors provide
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
3
  — so push them to provide recent stuff.
4 5 6 7 8 9 10 11 12
  Already, swank-asdf doesn't support anything older than 2.014.6
  (as provided by the first 2011 iteration of Quicklisp), and
  I (fare) am pushing for swank-asdf to not support anything older
  than 2.019 (still used by LispWorks 6.1).
  Hopefully, sometime in 2014, everyone will have adopted ASDF 3.
  Maybe remove old versions from upgrade tests; or maybe not:
  if we support old versions in any way,
  it should be for upgrade only, and "punt" is acceptable.
  Upgrade tests might be split in two test sets: short and long.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
13

14 15
* Moving toward cross-compilation (ASDF 3.2? 4?)
   This would allow to get most of the benefits of XCVB
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
16 17
   (reproducibility, scalability, applicability to mobile platforms, etc.),
   except without the backward incompatibility of XCVB.
18
   NB: the MOCL author would benefit a lot, and might chip in.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
19 20
** Need to further split asdf:perform in two parts:
   A part that runs on the host and specifies (as SEXP or string to read)
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64
   forms that must be evaluated on the target machine, not the host:
   (asdf:perform-forms target operation component)
   The default implementation can fallback to running the
   (asdf:perform operation component) on the target,
   which if it is on specially crafted operation and component objects
   that do not require recreating the component hierarchy and plan,
   but still require loading the defsystem-depends-on dependencies:
   on the target:

   (defmethod perform-forms ((target null) operation component)
     ;; null target designates current image
     `((asdf:perform ',op ',comp)))
   (defmethod perform-forms ((target external-target) operation component)
     ;; external target means a cross compiler
     `((require :asdf)
       (map () 'asdf:load-system '(,defsystem-deps))
       (asdf:perform ,(fake-operation-form operation)
                     ,(fake-component-form component))))

   The other way around the default perform method could be:

   (defmethod perform ((o t) (c t))
     (let ((forms (perform-forms nil o c)))
       (if (equal forms
                  `((asdf:perform ',o ',c)))
           (error "Missing perform method on ..." ...)
           (map () 'eval-thunk forms))))

   Note that in the general case, there are multiple forms,
   that must be provided on the command line somehow
   (see the lisp-invocation system and also how cl-launch does it),
   with packages necessary to read latter forms being
   created by former forms, so you cannot read everything in one go.
   ASDF or at least UIOP should probably be provided in the target
   image by default, anyway, without needing to be explicitly specified.
   A more declarative interface to needing the defsystem-deps
   is probably useful.
** A real cross-compiling backend that works the way of XCVB
   would need to compute a complete graph for the plan,
   which could be achieved by inheriting from the code in POIU.
   Thinking about it, the cross-compiling target object
   could actually be the same as the plan object.
   The basic case of in-image execution would need to be in ASDF,
   while the actual cross-compilation case would be in an extension.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
65
** Audit all the current specializers of perform, and offer them a new way;
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
66
   they can keep the perform method to run on older versions of ASDF.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
67 68
** Modify SBCL and other implementations so they provide UIOP
   independently from ASDF?
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
69

Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129
* Implementation bugs
** CMUCL has bugs:
*** In ASDF 2.32.13, sibling-dependencies is renamed to sideway-dependencies
    in defclass component, a superclass of system, and upgrade from
    2.32 or earlier thus fails with
    Error in function KERNEL:CLASS-TYPEP:  Class is currently invalid:
    #<KERNEL::STANDARD-CLASS ASDF/SYSTEM:SYSTEM {58398145}>
    in a direct call from ASDF/FIND-SYSTEM:LOCATE-SYSTEM,
    which suggests CMUCL's PCL fails to finalize classes properly.
*** Non-default optimize settings may or may not subtly break PCL.
    For the longest time (from 2.26.136 to 3.1.0.42), ASDF had:
    (declaim (optimize (speed 1) (safety 3) (debug 3)))
    This form may or may not work around that breakage in some cases:
    (setf c::top-level-lambda-max 0)
*** At some point there was massive breakage due to uninitialized slots
    as revealed in 3.1.0.37 with
    make t l=cmucl t=test-encodings.script
    which was a different PCL bug from the above (without same workaround)
    but possibly also triggered by the non-standard declaim.

** XCL has bad bugs:
   make-pathname doesn't handle :type nil properly and
   has massive lossage in logical-pathname support.
   If using block () and return in search-for-system-definition
   instead of return-from, XCL mistakenly has the return jump
   to the end of the try function or something.
   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?
   The backtrace frames may contains unprintable objects.
   make-pathname fails to copy the version from the defaults.
   (make-pathname :host "ASDFTEST" :directory '(:absolute "system2" "module4")
    :name nil :type nil) fails to handle the logical-pathname-ness of ASDFTEST.

** GCL is almost working again; but implementation bugs remain.
   See November 2013 discussion on gcl-devel.
    * Another GCL compiler bug:
    when I changed the definition of getcwd from
    (let ((*default-pathname-defaults* #p"")) (truename #p"")) to
    (let ((*default-pathname-defaults* *nil-pathname*)) (truename *nil-pathname*))
    to guard against e.g. a logical-pathname context while loading asdf
    and parsing #p"", calls to getcwd result in a segfault.
    * An another bug: gcl refuses dynamic-extent declaration on functions.
     uiop/stream.lisp:         #-gcl (declare (dynamic-extent ,@(when
     before `(#',beforef)) ,@(when after `(#',afterf))))
    * (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
    * 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")
    * Missing: chdir, combine-fasls, and plenty more UIOP functions.
    * Do whatever it takes to pass the asdf tests, add the above?
    * Have (require "asdf") and (require "ASDF") both work.
    * 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,
      rather than nil. This is probably a bug in #+ processing.
      Unhappily, debian creates such a file in
      /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),
      which suggests brokenness in handler-bind and/or error.

** Find out why ABCL fails the timestamp propagation test.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
130 131 132

* Find an easier way to bind variables around compilation and loading of files

Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
133 134 135 136 137
* Design & Implement some out-of-line configuration mechanism for various options?
  i.e. let configuration files override some variables around some actions.
  * Could be used to override new backward-incompatible defaults
   (e.g. for operation propagation, deferred warnings, etc.)
  * Use the above variable binding mechanism.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
138

139
* Fix bugs on http://bugs.launchpad.net/asdf/+bugs
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
140

141
* fix directory-files to not return directories on CCL, etc. Add tests.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
142

143
* use cl-test-grid to see if asdf-user can :use most (all?) of UIOP.
144 145 146 147 148
  SB-GROVEL used (until 25c1769 from 2013-02-23) to :use both ASDF and
  SB-EXT, which prevents ASDF from exporting RUN-PROGRAM, but
  should not be a problem with ASDF-USER :use'ing UIOP.
  A run of quicklisp is necessary, with an eye also for warnings
  from .asd's that might be overriding definitions in UIOP(!)
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
149

Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
150
* have a mode to explain WHY a component needs to be recompiled.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
151

152
* have a better defsystem form verifier - see lp#1007335
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
153

154 155 156
* 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.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
157

158
* have with-input-file use the encodings mechanism?
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
159

160
* have a single test .asd that tests as many features as possible, use it for upgrade test.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
161

162
* Bug found by fe[nl]ix: infinite loop if the definitions in an asd file
163 164 165
  are not in strict defsystem-depends-on dependency order.
** At least document the issue.
** Real solution: defer parsing and evaluation of defsystem forms.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
166

167
* Learn to use cl-grid-test, to make sure ASDF changes don't break stuff,
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
168
 and that breakage gets fixed quickly.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
169 170

* Include some ABL test for stassats's (now obsolete?) thing:
171 172
   (asdf:enable-asdf-binary-locations-compatibility
    :centralize-lisp-binaries t :default-toplevel-directory *fasl-dir*)
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
173

Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
174 175
* Make load-op a generic operation that selects the proper strategy
  for each system, module or file, according to component properties and user-configuration:
176
  compile the lisp file then load the fasl (load-fasl-op on a cl-source-file),
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
177
  load the lisp file without compiling (load-source-op),
178 179
  compile all files for the system, link them and load the result
   (load-fasl-op on the system),
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
180 181 182 183
  compile all files for the system *and* its dependencies, link and load (monolithic-load-fasl-op),
  concatenate all files for the system, then load the result (load-concatenated-source-op),
  concatenate all files for the system, then link them and load the result (load-compiled-concatenated-op),
  concatenate all files for the system *and* its dependencies, link and load (monolithic-load-compiled-concatenated-op).
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
184

185 186
* operation cleanup?
** Kill backward-compat functions after all clients have moved on.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
187
** Kill original-initargs -- BEWARE, it currently has clients!
188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214
** To allow semantically distinct operations of the same class:
You'd need to have a protocol to canonicalize them
in the *OPERATIONS* memoization table, not by class name,
but by CONS of the class name and some CANONICAL-OPERATION-INITARGS.
The latter would be a generic function called on the initargs,
where any parasite initargs such as FORCE and FORCE-NOT have been removed,
since they below to the PLAN, not the OPERATION:
the OPERATE protocol would be refined to explicit split
arguments to be passed to MAKE-PLAN or to MAKE-OPERATION.
The default method for CANONICAL-OPERATION-INITARGS
would SORT (a plist->alist of) the initargs,
and that would replace the current ORIGINAL-INITARGS slot.
For this scheme to work even in presence of undisciplined users
using MAKE-INSTANCE on an operation class,
the OPERATION class would have an extra slot EFFECTIVE-OPERATION,
uninitialized by default (nil or unbound), whose accessor initializes it
if it's uninitialized, by looking up a canonical instance in *OPERATIONS*,
and if unfound registering the current operation as canonical.
Then, each component's COMPONENT-OPERATION-TIME hash-table
would be indexed by canonicalized operation object
rather than by operation class,
and POIU would have to be changed accordingly.
Of course, this entire cleanup is incompatible
with how SWANK and GBBopen currently abuse slots of operation,
so these would have to be fixed first.
And that's why I didn't do it.
It looks like SWANK can be fixed soon, though, so we'll see.
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
215

216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286
* Get rid of component-properties
** directly use component-properties:
*** yaclml.asd => misguided :features for version comparison
*** amazon-ecs-20110418-git/amazon-ecs.asd => :website property
*** hemlock.asd => bad implementation of latin1 encodings
** .asd use :properties
*** arnesi, arnesi+ => :features, misguided for version comparison and pseudo #+features
*** lkcas, thopter => :long-name
*** cl-irc cliki-bot rss cl-syslog com.informatimago.clext
   com.informatimago.clisp com.informatimago.clmisc
   com.informatimago.common-lisp.arithmetic
   om.informatimago.common-lisp.bank
   com.informatimago.common-lisp.cesarum
   com.informatimago.common-lisp com.informatimago.common-lisp.csv
   com.informatimago.common-lisp.cxx
   com.informatimago.common-lisp.data-encoding
   com.informatimago.common-lisp.diagram
   com.informatimago.common-lisp.ed
   com.informatimago.common-lisp.graphviz
   com.informatimago.common-lisp.heap
   com.informatimago.common-lisp.html-base
   com.informatimago.common-lisp.html-generator
   com.informatimago.common-lisp.html-parser
   com.informatimago.common-lisp.http
   com.informatimago.common-lisp.interactive
   com.informatimago.common-lisp.invoice
   com.informatimago.common-lisp.lisp
   com.informatimago.common-lisp.lisp.ibcl
   com.informatimago.common-lisp.lisp.stepper
   com.informatimago.common-lisp.lisp-reader
   com.informatimago.common-lisp.lisp-sexp
   com.informatimago.common-lisp.lisp-text
   com.informatimago.common-lisp.parser
   com.informatimago.common-lisp.picture
   com.informatimago.common-lisp.regexp
   com.informatimago.common-lisp.rfc2822
   com.informatimago.common-lisp.rfc3548
   com.informatimago.common-lisp.telnet
   com.informatimago.common-lisp.unix
   linc
   com.informatimago.lispdoc
   com.informatimago.lua
   com.informatimago.cocoa-playground
   com.informatimago.objcl
   com.informatimago.rdp
   com.informatimago.rdp.basic
   com.informatimago.rdp.basic.example
   com.informatimago.rdp.example
   com.informatimago.susv3
   com.informatimago.common-lisp.tools.make-depends
   com.informatimago.xcode
   spartns
   xlunit
   => (uninterned!)
   #:author-email #:date
   (#:albert #:output-dirs)
   (#:albert #:formats)
   (#:albert #:docbook #:template)
   (#:albert #:docbook #:bgcolor)
   (#:albert #:docbook #:textcolor)
   (#:albert #:docbook #:dtd)
*** portableaserve
   =>
   ("system" "author" "email")
   ("albert" "presentation" "output-dir")
   ("albert" "presentation" "formats")
   ("albert" "docbook" "dtd")
   ("albert" "docbook" "template")
*** com.clearly-useful.generic-collection-interface => :com.clearly-useful
*** metatilities
   => :ait-timeout :system-applicable-p
287
*** ucw ucw-core
288 289
   =>
   version
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
290 291 292

* ASDF4: search for this tag, rename things (incompatibly, thus) and cleanup code.

293 294
* 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
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
295 296 297

* deferred-warnings support probably needs to be redone better.
  * implement deferred warnings support on lispworks
298
  * turn undefined function style-warnings into full warnings(?)
Francois-Rene Rideau's avatar
Francois-Rene Rideau committed
299 300 301 302
  * work with cl-test-grid to eliminate deferred warnings from quicklisp libraries
  * 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.