- Dec 01, 2003
-
-
Daniel Barlow authored
-
- Aug 05, 2003
-
-
Kevin Rosenberg authored
-
- Jun 03, 2003
-
-
Daniel Barlow authored
make SBCL require hook a lot quieter, by muffling style-warnings when loading files and turning off asdf verbosity
-
- May 28, 2003
-
-
Kevin Rosenberg authored
Document these variables in the README
-
- May 27, 2003
-
-
Kevin Rosenberg authored
(Should this variable be exported?)
-
- Mar 17, 2003
-
-
Daniel Barlow authored
-
- Mar 16, 2003
-
-
Daniel Barlow authored
if unsupplied Shuffle some definitions around to reduce 'not defined yet' complaints Changes to :force option on operations - ':force t' is no longer passed onto dependent systems ':force (system1 system2 ...systemn)' is a list of system names to be forced ':force :all' is the original force-everything-recursively behaviour
-
- Feb 08, 2003
-
-
Daniel Barlow authored
Some glue that won't affect too many people but that lets ASDF cleanly hook the extensible PROVIDE/REQUIRE mechanism in upcoming SBCL 0.7.13 Fix wild-modules to not object when we call (setf (module-components)) on a new or about-to-be-reinitialised module. We need to be able to do this to get the weeds out, so it should be legal
-
- Feb 04, 2003
-
-
Daniel Barlow authored
*central-registry* no longer takes functions (that feature was broken anyway), but a new list *system-definition-search-functions* does. Its default content is a single function designator for sysdef-central-registry-search, which does the *central-registry* search Update documentation to match Fix test1.script to call the preferred OPERATE instead of OOS Update documentation to describe COMPONENT-PROPERTY method
-
- Nov 12, 2002
-
-
Daniel Barlow authored
- now it takes two arguments not three - and returns (operation . component) pairs - which don't include pruned-ops Sorted out some load-op methods to use input-files instead of faking their own compile-ops just to find out what the input files are
-
- Nov 08, 2002
-
-
Daniel Barlow authored
shouldn't do global proclamations, that's bad karma (reported by Gary Byers) modules maybe now can have no components (Matthew Danish, SF bug id 625738) (added an :initform nil, haven't actually tested) significant reworking to handle recompilation of dependencies properly - use of component properties for last-compiled/last-loaded is gone - new internal gf INPUT-FILES (COMPONENT OPERATION) - TRAVERSE doesn't actually perform anything, but it now has a defined return value: a list of the ops and components that need doing. OPERATE loops over answers from TRAVERSE - intended to have no user-visible effects, but ICBW! May break existing systems! - still doesn't do cross-module dependencies properly, sigh. but we're closer - default output-files method now returns NIL instead of causing an error
-
- Aug 28, 2002
-
-
Daniel Barlow authored
-
Daniel Barlow authored
-
Daniel Barlow authored
-
- Aug 23, 2002
-
-
Kevin Rosenberg authored
-
- Jun 19, 2002
-
-
Daniel Barlow authored
-
- Jun 08, 2002
-
-
Daniel Barlow authored
Merge compiler warning cleanups from Miles Egan in mail message-id <20020607203531.GE9363@pixar.com> Add elementary CVS instructions to README file
-
- Apr 30, 2002
-
-
Daniel Barlow authored
Several changes * If some component of *central-registry* is a function or a symbol for which fboundp returns true, it will be funcalled with the system name string as an argument, and should return a directory in which to look for the system definition. This allows much more flexibility in the location of .asd files * New component type 'system' is functionally identical to module, but has attributes for author name, licence, description etc, which can be used by programs that make platform packages * Much shuffling of parts of the file so that it compiles without any warnings about forward declarations * The behaviour when compile-file returns non-NIL in its secondary values (failure-p and warnings-p) can now be customized: new compile-op initargs :on-warnings and :on-failure take values (or :warn :error :ignore). If unspecified, these default to *compile-file-{failure,warnings}-behaviour* * A new 'properties' attribute to component which can be used to communicate extra optional information between system authors and platform package creation programs
-
- Mar 06, 2002
-
-
Daniel Barlow authored
-
Daniel Barlow authored
sorted out the component case slop
-
- Feb 28, 2002
-
-
Daniel Barlow authored
+** proclamations probably aren't
-
- Feb 20, 2002
-
-
Daniel Barlow authored
-
- Feb 19, 2002
-
-
Daniel Barlow authored
- tetsing implementation features - version dependencies (doesn't yet work) - and/or dependencies (likewise, nonfunctional) proposed asdf system standard moved onto a cliki page
-
- Feb 14, 2002
-
-
Daniel Barlow authored
-
Daniel Barlow authored
-
Daniel Barlow authored
-
- Feb 12, 2002
-
-
Daniel Barlow authored
-
Daniel Barlow authored
-
- Feb 11, 2002
-
-
Daniel Barlow authored
-
- Aug 20, 2001
-
-
Christophe Rhodes authored
anaphorically captured as asdf:component). Implemented :perform and :explain defsystem arguments as in (slightly adjusted) README Also added :initially-do and :finally-do mk-compatibility options
-
- Aug 06, 2001
-
-
Daniel Barlow authored
+** operation instantiation in traverse sucks
-
Daniel Barlow authored
(operation component) pairs, not just components.
-
- Aug 03, 2001
-
-
Daniel Barlow authored
-
Daniel Barlow authored
-
- Aug 02, 2001
-
-
Daniel Barlow authored
-collection of source files. +collection of components. "We extend the defsystem syntax to allow for eql-specialised methods on modules": updated to fit current operation abstraction symbols vs strings: Warn the user that they should either use keywords or be careful with the package that they evaluate defsystem forms in the :pathname argument is misnamed
-
- Aug 01, 2001
-
-
Daniel Barlow authored
-