asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

[asdf-devel] Output Stream for ASDF
by thomas.bartscher＠widder-software.com 30 Nov '09

30 Nov '09

Why are warnings of asdf put into *standard-output*? Wouldn't it be easier to put those into something like *asdf-warnigs*? This way users of asdf could redirect those wherever they want.

3 2

[asdf-devel] duplicate-names for module and file with same name?
by Jianshi Huang 27 Nov '09

27 Nov '09

Hi, Currently in parse-component-form function, duplication of names are checked but modules and files are put to the same category. Is there any particular reason for this restriction? e.g. I can't have both foo.lisp foo/ in the same folder since (:module :foo) and (:file "foo") will conflict in names. Cheers, Jianshi Huang

2 2

[asdf-devel] ASDF::COERCE-NAME string-downcases symbols, but lets strings untouched
by Tobias C. Rittweiler 21 Nov '09

21 Nov '09

(defun coerce-name (name) (typecase name (component (component-name name)) (symbol (string-downcase (symbol-name name))) (string name) (t (sysdef-error "~@<invalid component designator ~A~@:>" name)))) I first thought this was some bad kludge to support modern-mode. But vc-annotate told me that was introduced by Nikodemus. What is the reason that symbols are downcased but strings not? It makes (FIND-SYSTEM :FOO) be different from (FIND-SYMBOL (SYMBOL-NAME :FOO)) which is just weird. -T.

3 3

[asdf-devel] broken texinfo link
by nuntius＠strider2.example.org 20 Nov '09

20 Nov '09

asdf.texinfo still refers to Kent's old site at http://world.std.com/~pitman/Papers/Large-Systems.html It should be updated to http://nhplace.com/kent/Papers/Large-Systems.html - Daniel

2 1

[asdf-devel] update defsystem grammar for method forms
by Robert P. Goldman 20 Nov '09

20 Nov '09

I was trying to write some in-line method definitions in defsystem and found that the system grammar supplied in the manual did not specify the grammar for this. The grammar is actually a little tricky, and doesn't support specifying primary methods, so I think an extension to the docs is warranted. Best, r

1 1

[asdf-devel] Patch for buggy URL in asdf.texinfo
by Robert P. Goldman 20 Nov '09

20 Nov '09

Nuntius provided a patch for an out-of-date pointer to Kent Pitman's paper in asdf.texinfo. Here's a patch for that.

1 1

[asdf-devel] First steps for ECL support
by Juan Jose Garcia-Ripoll 17 Nov '09

17 Nov '09

I have split the change into two, as I normally do in the ECL source tree itself. The first change only pertains asdf.lisp and it adds a slot, FLAGS, to COMPILE-OP. These are additional flags for COMPILE-FILE. It is used by ECL because we want to produce two files per source file: an object file and the FASL itself. These files can be separately used for building larger things (shared libraries, programs...) or for immediate loading. The second set of changes is isolated in a single file, asdf-ecl.lisp, which is more complex. This file contains a number of extensions, which may or may not be adapted to other platforms (I believe it is possible, at least for some things). What it implements: - COMPILED-FILE, a new component for distribution of pre-compiled files. I use it to build pre-packaged versions of RT, the compiler and other things that now can be included as dependencies. - A number of operations for creating shared libraries, programs, etc. These operations use traverse in a funny way to find out the order in which files should be combined. I call them BUNDLEs because the result is a single binary file that combines many lisp sources, compiled. It has an important advantage for ECL, apart from distribution, for it takes less resources to load a single file. - A function, MAKE-BUILD, which uses those operations hiding the details. - A new operation, LOAD-FASL-OP, which uses those "bundles". - A hook into REQUIRE using LOAD-FASL-OP. What is implemented more or less follows this http://ecls.sourceforge.net/new-manual/ch16.html Comments are welcome. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

2 1

[asdf-devel] Two questions
by Nick Levine 17 Nov '09

17 Nov '09

1. Problems with the :feature feature. (asdf:defsystem foo :components ((:file "pkg") (:file "code") (:file "foo" :depends-on ((:feature :frob))))) If :frob is not on *features*, load-system gives me: Error: Bad dependency (FEATURE FROB). Dependencies must be (:version <version>), (:feature <feature>), or a name If :frob is a *feature* I get a different error: Error: Error component :FROB not found, required by #<CL-SOURCE-FILE "foo" #x8B7A3E6> Did I misunderstand something? 2. Suppose I would like some code to run at compile-time / load-time to determine where the fasls should live (e.g. hypothetically, in a subdirectory named after a timestamp, or according to what patches I have loaded). How do I express this? (I'm using version 1.363) Thanks. - nick

8 16

[asdf-devel] performance of find-system (on sbcl)
by Attila Lendvai 16 Nov '09

16 Nov '09

dear list, find-system is so slow that i took the time to look into it. this is what i've used to test: (sb-sprof:with-profiling () (trace sb-fasl::load-as-source) (time (labels ((recurse (system-name) (let ((system (asdf:find-system system-name nil))) (dolist (child (rest (first (asdf:component-depends-on 'asdf:compile-op system)))) (recurse (asdf:find-system child nil)))))) (recurse (asdf:find-system :hu.dwim.walker nil))))) out of the box run: Evaluation took: 3.233 seconds of real time 2.350000 seconds of total run time (2.120000 user, 0.230000 system) [ Run times consist of 0.410 seconds GC time, and 1.940 seconds non-GC time. ] 72.69% CPU 15,573 forms interpreted 2,688 lambdas converted 5,615,673,160 processor cycles 15 page faults 128,748,160 bytes consed when adding the following to asdf:find-system, just around the cl:load call: #+sbcl (sb-ext:*evaluator-mode* :interpret) Evaluation took: 1.506 seconds of real time 0.740000 seconds of total run time (0.640000 user, 0.100000 system) [ Run times consist of 0.110 seconds GC time, and 0.630 seconds non-GC time. ] 49.14% CPU 16,582 forms interpreted 56 lambdas converted 2,764,841,332 processor cycles 2 page faults 58,959,808 bytes consed any thoughts on this? -- attila

2 2

[asdf-devel] problems defining a new component class
by Robert Goldman 13 Nov '09

13 Nov '09

I'm finding that for some reason the :default-initargs to a new component class (a subclass of cl-source-file) I've defined are not getting applied. I have a vague memory that there's some weirdness in the way asdf creates components that means that this doesn't work, but I'd be obliged if anyone could provide more guidance. In particular, I would be very grateful for any suggested workaround if, as I suspect, this is something that ASDF simply won't let me do. many thanks, r

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel