asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

Re: Intended behavior of *COMPILE-FILE-WARNINGS-BEHAVIOUR*
by Faré 15 Jan '16

15 Jan '16

[This was my reply that bounced yesterday. I edited it.] On 1/14/16 Jan 14 -1:20 PM, Robert Goldman wrote: > What is the intended behavior when this is bound to :IGNORE? > > I believe that if warnings occur, they should be quashed and > COMPILE-FILE should still return T, although otherwise it would not. > Yes, the intent is that in case of :IGNORE, the compilation should just succeed (assuming an output file was returned). > I'm finding a case where :IGNORE is not enough to make the compile-file > succeed, but I'm grappling with trying to find a minimal test case. So > I was wondering if I was interpreting this variable correctly. > Either no .fasl was created, or you found another bug in UIOP. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The uploaded man cut himself from the world. The optimizer saw the simulation would have no more side-effects and optimized it all away.

1 0

Re: Intended behavior of *COMPILE-FILE-WARNINGS-BEHAVIOUR*
by Robert Goldman 15 Jan '16

15 Jan '16

[... this message also bounced yesterday...] On 1/14/16 Jan 14 -1:20 PM, Robert Goldman wrote: > What is the intended behavior when this is bound to :IGNORE? > > I believe that if warnings occur, they should be quashed and > COMPILE-FILE should still return T, although otherwise it would not. > > I'm finding a case where :IGNORE is not enough to make the compile-file > succeed, but I'm grappling with trying to find a minimal test case. So > I was wondering if I was interpreting this variable correctly. > > thank you > The relevant bit of the manual describes acceptable values for this variable and COMPILE-FILE-FAILURE-BEHAVIOUR, but does not explain their semantics: ASDF checks for warnings and errors when a file is compiled. The variables *COMPILE-FILE-WARNINGS-BEHAVIOUR* and *COMPILE-FILE-FAILURE-BEHAVIOUR* control the handling of any such events. The valid values for these variables are ':error', ':warn', and ':ignore'.

1 0

Intended behavior of *COMPILE-FILE-WARNINGS-BEHAVIOUR*
by Robert Goldman 15 Jan '16

15 Jan '16

[This message bounced yesterday for some reason] What is the intended behavior when this is bound to :IGNORE? I believe that if warnings occur, they should be quashed and COMPILE-FILE should still return T, although otherwise it would not. I'm finding a case where :IGNORE is not enough to make the compile-file succeed, but I'm grappling with trying to find a minimal test case. So I was wondering if I was interpreting this variable correctly. thank you

1 0

Test
by Erik Huelsmann 15 Jan '16

15 Jan '16

Test

1 0

Where is cl-launch.asd?
by Robert Goldman 12 Jan '16

12 Jan '16

I tried to load the asdf tools interactively, under SLIME, and they fail to launch, although everything seems to run from make. I get this error: Component "cl-launch/dispatch" not found, required by #<PACKAGE-INFERRED-SYSTEM "cl-scripting/commands"> and, indeed: ~/lisp/asdf/ext/cl-launch $ find . -name '*.asd' ~/lisp/asdf/ext/cl-launch $ I see this: ~/lisp/asdf/ext/cl-launch $ git status HEAD detached at 220b8ca nothing to commit, working directory clean ~/lisp/asdf/ext/cl-launch $ Is this another oddity of git submodules? Is the version of cl-launch in our git repo not sufficiently up-to-date? Actually, when I look at xcvb/cl-launch, there is no cl-launch.asd there, either. This is crippling my ability to fix 1532464

4 6

Moving towards resignation
by Robert Goldman 12 Jan '16

12 Jan '16

I am now very unhappy with my role as maintainer. Over my repeated expressions of concern, the minimakefile -- which aims to replace normal shell tools with CL-based scripting facilities -- has been merged with core ASDF. Since then, almost all of my ASDF-related time has gone into wrestling with said scripting facilities. I don't mind if people think it's cool to try to make a CL scripting facility. But it's not my thing. I just want my tools to work. The CL scripting facility is, IMO, at an "alpha" level in which it works acceptably in the developer's environment, but can be expected to hiccup seriously anywhere else. I don't want to fight it any more. So I'm offering the community two choices: 1. I "un-merge" the minimakefile facilities and go back to vanilla CL and the standard Unix toolkit for maintenance. 2. Someone emerges to take over the maintenance of ASDF in its current shape, and I go back to being a simple contributor. I barely have enough time to keep up my responsibilities as maintainer; I simply don't have the time to maintain cl-launch, cl-scripting, yadda yadda yadda, as well as ASDF. Even if I did, I wouldn't want to, because this is not a direction that interests me personally. I don't say it's a wrong direction, just that it's not my thing. Fare likes this structure, and he is still the master of ASDF. Me handing off ASDF is more survivable than driving Fare away. So I believe that finding a maintainer who is intrigued by the new direction, and enjoys moving it forward, is a better choice than going back and ripping out the new framework (in retrospect, we should have *added* the new scripting facilities, rather than *replacing* the old). So consider this a call for my replacement. It's been an interesting ride, and I have learned a lot in the process, but it's probably time for someone else, who's more motivated by the new infrastructure. Best, R

3 2

bug: after erring on undefined component type, system is reported to load successfully
by 73budden . 10 Jan '16

10 Jan '16

Version 3.1.5, Example system definition: (defsystem :s3 :components ((cl-user::cons "file-name-does-not-matter") )) ;; eof I try to load it, it says: "Error while trying to load definition for system s3 from pathname c:/clcon/lp/test/s3.asd: don't recognize component type CONS" Then I try to load it another time, it says: T

2 3

user-homedir-pathname on cmucl
by Raymond Toy 09 Jan '16

09 Jan '16

Not sure how this ever worked with cmucl, but user-homedir-pathname on cmucl returns #p"home:", where "home:" is a search-list. In some cases, it looks like asdf is trying to create the cache directory and end up with a path like P"home:.cache/common-lisp/cmu-21a__21a_unicode_-macosx-x86/**/*.*.~*~" but this confuses other parts of asdf and cmucl when trying to run pathname-match-p. Perhaps the best thing is to make asdf us a custom user-homedir-pathname like what is done with other lisps. An appropriate version would be (defun user-homedir-pathname () (first (ext:search-list (cl:user-homedir-pathname)))) -- Ray

2 13

I believe that load-system is described incorrectly in the manual
by 73budden . 08 Jan '16

08 Jan '16

Quote from the manual: "But for code that you are actively developing, debugging, or otherwise modifying, you should use load-system, so ASDF will pick on your modifications and transitively re-build the modified files and everything that depends on them. " What does "everything that depends on them" mean? I have sys1.asd: (asdf:defsystem :sys1 :serial t :components ((:file "sys1-file1"))) ; EOF and sys2.asd (asdf:defsystem :sys2 :serial t :depends-on (:sys1) :components ((:file "sys2-file2"))) ; EOF I do (asdf:load-system :sys2), then I touch sys1-file1.lisp, then I do (asdf:load-system :sys1) :sys2 does not get recompiled. This is what I always knew and expected to see, but, according to manual, it should have been recompiled, as :sys2 depends on :sys1, and, hence, from the modified sys1-file1.lisp. Now I don't know is this a "misbug" in asdf or a defeciency in the manual. If this is a misbug, another question arises: is there a "canonical" way to reload all systems that are currently loaded into the image and sources of which have changed since last load?

2 1

uiop parse-native-namestring portability?
by Jared C. Davis 08 Jan '16

08 Jan '16

Hi, Should I be able to expect the following to behave consistently across Lisps? (file-namestring (uiop:parse-native-namestring ".")) I find that: - CCL and SBCL produce "." - Allegro produces NIL - CMUCL signals an error in LISP::UNPARSE-UNIX-FILE If I just look at: (uiop:parse-native-namestring ".") I get: Allegro: #P"./" CCL: #P"." SBCL: #P"." CMUCL: #P(:NAME "." :TYPE :UNSPECIFIC) Cheers, Jared -- Jared C. Davis <jared(a)cs.utexas.edu> 11410 Windermere Meadows Austin, TX 78759 http://www.cs.utexas.edu/users/jared/

4 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel