- 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
-
- Mar 07, 2003
-
-
Christophe Rhodes authored
".sbcl/systems", duh)
-
- Mar 04, 2003
-
-
Kevin Rosenberg authored
Incorporate patch for 'load-source-op. This may benefit from some rewriting, but this code clearly works better than the existing stub code.
-
- Mar 03, 2003
-
-
Kevin Rosenberg authored
-
- Feb 13, 2003
-
-
Christophe Rhodes authored
justification routines. Sucky thing I: CLISP dislikes calls to FORMAT with pretty-print format strings. Bizarrely, though, it accepts calls to FORMATTER with the same format strings. So use FORMATTER everywhere to keep clisp happy. Sucky thing II: CMUCL can't do ENOUGH-NAMESTRING, because it has this weird ~UNSPECIFIC~ thing in its *DEFAULT-PATHNAME-DEFAULTS*. So don't use ENOUGH-NAMESTRING, even though it's crying out for it.
-
- 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
-
- Jan 28, 2003
-
-
Daniel Barlow authored
specialisation on (stream stream), because STREAM is not a class. The workaround is harmless anyway: just remove the specialisation
-
- Dec 09, 2002
-
-
Daniel Barlow authored
-
- Dec 02, 2002
-
-
Kevin Rosenberg authored
-
- Nov 23, 2002
-
-
Kevin Rosenberg authored
-
- Nov 18, 2002
-
- 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
-
- Sep 20, 2002
-
-
Kevin Rosenberg authored
-
Daniel Barlow authored
-
Kevin Rosenberg authored
-
Kevin Rosenberg authored
-
Daniel Barlow authored
-
- Sep 17, 2002
-
-
Kevin Rosenberg authored
-
Kevin Rosenberg authored
-
- Sep 13, 2002
-
-
Daniel Barlow authored
-
Kevin Rosenberg authored
-
Daniel Barlow authored
death to LPNs! revert change to system-definition-pathname that was causing lossage when used with physical pathnames
-
- Sep 12, 2002
-
-
Kevin Rosenberg authored
Kludge in :version to get CLC LPN to work with CMUCL. This may be a temporary change if a bug in CMUCL's handling of LPN's is found when :version is :newest
-
- Sep 09, 2002
-
-
Daniel Barlow authored
-
- Aug 30, 2002
-
-
Kevin Rosenberg authored
-
Kevin Rosenberg authored
-
- Aug 28, 2002
-
-
Daniel Barlow authored
-
Daniel Barlow authored
similar which corresponds to the CVS revision of asdf.lisp - compile-file errors The default behaviour for coping with compile-file errors has changed: (defvar *compile-file-warnings-behaviour* :warn) -(defvar *compile-file-failure-behaviour* :error) +(defvar *compile-file-failure-behaviour* #+sbcl :error #-sbcl :warn) Most lisp implementations (all that I know of except for sbcl) stop and enter the debugger for catastrophic errors in file compilation. SBCL otoh has a much finer warning/style-warning distinction and should not ever return failure-p unless for a catastrophic error Fix printing of system-definition-error in CMUCL (thanks to Bob Rogers) Moved a lot of messing around with 'last-compiled and 'last-loaded properties into :before and :after methods on source-file so that "don't reload if already loaded" works for new source file types that users create There is a new operation load-source-op based on Kevin Rosenberg's implementation of same. I'm not altogether sure yet how this should interact with 'last-compiled and 'last-loaded: suggestions welcomed OPERATE now does the operation inside a WITH-COMPILATION-UNIT form, to reduce noise from the compiler about forward definitions. Courtesy of Bob Rogers
-
- Aug 26, 2002
-
-
Kevin Rosenberg authored
-
- Aug 18, 2002
-
-
Kevin Rosenberg authored
-
Kevin Rosenberg authored
-
- Jul 04, 2002
-
- Jun 19, 2002
-
-
Daniel Barlow authored
("asdf:defsystem class bug")
-
- 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
-
- May 20, 2002
-
-
Daniel Barlow authored
avoid reloading files that have already been loaded into the image. based on a patch by Brian Seitz
-
Daniel Barlow authored
before the dependency is looked for This patch does the coercion at lookup time even though it would be better done earlier, because the in-order-to syntax is insanely complicated. In a future version we may lose and/or dependencies; it's not as if anyone understands them anyway
-
- May 03, 2002
-
-
Daniel Barlow authored
-
Daniel Barlow authored
-