Preliminary analysis of existing ASDF practices
in [Lisp]
|
Prev: Is LISP divine?
Next: keywords & macros
From: Rainer Joswig on 19 Apr 2010 16:27 In article <87ochfwfmy.fsf(a)padme.localdomain>, m_mommer(a)yahoo.com (Mario S. Mommer) wrote: .... > > Please, using the same example you used above, give an example of > > how you would express these dependencies using your model so that we can > > better understand. > > As an extension of the defsystem notation: > > (requires (compile "file1.lisp") > (load "macros.lisp") > (load "packages.lisp")) > > I agree that this is not too cool ;-). But how about this: > > (let ((files > "packages" "macros" > "file1" "file2")) ;; etc. A directory listing would be > ;; better, probably > > (load-if-source-is-newer "packages.lisp") > (load-if-source-is-newer "macros.lisp") > > ;; You can even write a helpful comment here, explaining why you need > ;; the macros.lisp file before compiling other stuff. It even feels > ;; natural. > (mapcar #'compile-file-if-source-is-newer files) > (mapcar #'load-file-if-fasl-is-newer files)) Are you aware that this already exists in the DEFSYSTEMs of Symbolics Genera, LispWorks Allegro CL? -- http://lispm.dyndns.org/
From: Mario S. Mommer on 19 Apr 2010 16:57 Rainer Joswig <joswig(a)lisp.de> writes: > In article <87ochfwfmy.fsf(a)padme.localdomain>, > m_mommer(a)yahoo.com (Mario S. Mommer) wrote: >> [...] > Are you aware that this already exists in the DEFSYSTEMs of Symbolics > Genera, LispWorks Allegro CL? No. What exactly, the imperative compiler/loader, or the other idea?
From: Rainer Joswig on 19 Apr 2010 17:54 In article <87r5mbgnys.fsf(a)padme.localdomain>, m_mommer(a)yahoo.com (Mario S. Mommer) wrote: > Rainer Joswig <joswig(a)lisp.de> writes: > > In article <87ochfwfmy.fsf(a)padme.localdomain>, > > m_mommer(a)yahoo.com (Mario S. Mommer) wrote: > >> [...] > > Are you aware that this already exists in the DEFSYSTEMs of Symbolics > > Genera, LispWorks Allegro CL? > > No. What exactly, the imperative compiler/loader, or the other idea? The description of dependencies for various actions. -- http://lispm.dyndns.org/
From: Raymond Toy on 19 Apr 2010 18:50 On 4/19/10 5:54 PM, Rainer Joswig wrote: > In article <87r5mbgnys.fsf(a)padme.localdomain>, > m_mommer(a)yahoo.com (Mario S. Mommer) wrote: > >> Rainer Joswig <joswig(a)lisp.de> writes: >>> In article <87ochfwfmy.fsf(a)padme.localdomain>, >>> m_mommer(a)yahoo.com (Mario S. Mommer) wrote: >>>> [...] >>> Are you aware that this already exists in the DEFSYSTEMs of Symbolics >>> Genera, LispWorks Allegro CL? >> >> No. What exactly, the imperative compiler/loader, or the other idea? > > The description of dependencies for various actions. > Does that mean mk:defsystem has these features? The comments in mk:defsystem says the syntax was inspired by the defsystem from Symbolics 3600 and improves on it as well as the PCl defsystem. Ray, who uses mk:defsystem because there was no asdf when he started using defsystems.
From: Rainer Joswig on 19 Apr 2010 20:03
In article <sKmdnVRoyOnbQ1HWnZ2dnUVZ_hqdnZ2d(a)earthlink.com>, Raymond Toy <toy.raymond(a)gmail.com> wrote: > On 4/19/10 5:54 PM, Rainer Joswig wrote: > > In article <87r5mbgnys.fsf(a)padme.localdomain>, > > m_mommer(a)yahoo.com (Mario S. Mommer) wrote: > > > >> Rainer Joswig <joswig(a)lisp.de> writes: > >>> In article <87ochfwfmy.fsf(a)padme.localdomain>, > >>> m_mommer(a)yahoo.com (Mario S. Mommer) wrote: > >>>> [...] > >>> Are you aware that this already exists in the DEFSYSTEMs of Symbolics > >>> Genera, LispWorks Allegro CL? > >> > >> No. What exactly, the imperative compiler/loader, or the other idea? > > > > The description of dependencies for various actions. > > > > Does that mean mk:defsystem has these features? The comments in > mk:defsystem says the syntax was inspired by the defsystem from > Symbolics 3600 and improves on it as well as the PCl defsystem. The Symbolics DEFSYSTEM (a part of the System Construction Tool (SCT)) is in many ways quite different from mk:defsystem. The dependency description of mk:defsystem is based on the structure of the modules and systems. To answer your question, it lacks these features. The Symbolics defsystem dependencies are based on operations. To define the operation dependencies the Symbolics defsystem provides a short form (:serial, :parallel, ...) and a long form, where these dependencies between actions can be written in detail. ... (:in-order-to (:load :compile) (:load defs)) (:in-order-to :compile (:load macros)) ... > Ray, who uses mk:defsystem because there was no asdf when he started > using defsystems. -- http://lispm.dyndns.org/ |