Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asdf
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Didier Verna
asdf
Commits
eb0afa82
Commit
eb0afa82
authored
11 years ago
by
Francois-Rene Rideau
Browse files
Options
Downloads
Patches
Plain Diff
Documentation tweak.
parent
e6b5d611
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
TODO
+22
-1
22 additions, 1 deletion
TODO
doc/asdf.texinfo
+11
-1
11 additions, 1 deletion
doc/asdf.texinfo
with
33 additions
and
2 deletions
TODO
+
22
−
1
View file @
eb0afa82
...
@@ -33,7 +33,28 @@
...
@@ -33,7 +33,28 @@
:name nil :type nil) fails to handle the logical-pathname-ness of ASDFTEST.
:name nil :type nil) fails to handle the logical-pathname-ness of ASDFTEST.
* GCL is almost working again; but implementation bugs remain.
* GCL is almost working again; but implementation bugs remain.
See November 2013 discussion on gcl-devel
See November 2013 discussion on gcl-devel.
* Another GCL compiler bug:
when I changed the definition of getcwd from
(let ((*default-pathname-defaults* #p"")) (truename #p"")) to
(let ((*default-pathname-defaults* *nil-pathname*)) (truename *nil-pathname*))
to guard against e.g. a logical-pathname context while loading asdf
and parsing #p"", calls to getcwd result in a segfault.
* An another bug: gcl refuses dynamic-extent declaration on functions.
uiop/stream.lisp: #-gcl (declare (dynamic-extent ,@(when
before `(#',beforef)) ,@(when after `(#',afterf))))
* (typep p 'logical-pathname) should be T if p has a logical-pathname host.
* apropos is case-sensitive and returns a same symbol many times
* compile-file fails to return proper secondary values in case of non-style WARNING.
* (pathname-directory #p"foo/") is incorrectly ("foo") instead of (:RELATIVE "foo")
* Missing: chdir, combine-fasls, and plenty more UIOP functions.
* Do whatever it takes to pass the asdf tests, add the above?
* Have (require "asdf") and (require "ASDF") both work.
* Trying to uiop:slurp-stream-forms from a stream with #+(or) :foo
(or read-file-forms from an file with same) results in an error,
rather than nil. This is probably a bug in #+ processing.
Unhappily, debian creates such a file in
/etc/common-lisp/asdf-output-translations.conf.d/01-common-lisp-controller.conf
* Some out-of-line configuration mechanism for various options?
* Some out-of-line configuration mechanism for various options?
i.e. let configuration files override some variables around compilation of some systems.
i.e. let configuration files override some variables around compilation of some systems.
...
...
This diff is collapsed.
Click to expand it.
doc/asdf.texinfo
+
11
−
1
View file @
eb0afa82
...
@@ -4296,7 +4296,10 @@ Since ASDF 2,
...
@@ -4296,7 +4296,10 @@ Since ASDF 2,
it should always be a good time to upgrade to a recent version of ASDF.
it should always be a good time to upgrade to a recent version of ASDF.
You may consult with the maintainer for which specific version they recommend,
You may consult with the maintainer for which specific version they recommend,
but the latest @code
{
release
}
should be correct.
but the latest @code
{
release
}
should be correct.
We trust you to thoroughly test it with your implementation
Though we do try to test ASDF releases against all implementations that we can,
we may not be testing against all variants of your implementation,
and we may not be running enough tetst;
we trust you to thoroughly test it with your own implementation
before you release it.
before you release it.
If there are any issues with the current release,
If there are any issues with the current release,
it's a bug that you should report upstream and that we will fix ASAP.
it's a bug that you should report upstream and that we will fix ASAP.
...
@@ -4351,6 +4354,13 @@ and you are welcome to include @file{asdf.asd} amongst them.
...
@@ -4351,6 +4354,13 @@ and you are welcome to include @file{asdf.asd} amongst them.
Non-magic systems should be at the back of the @code
{
wrapping-source-registry
}
Non-magic systems should be at the back of the @code
{
wrapping-source-registry
}
while magic systems are at the front.
while magic systems are at the front.
@item
Since ASDF 3, the library UIOP comes transcluded in ASDF.
But for extra brownies, you may package UIOP separately,
so that one may @code
{
(require "uiop")
}
and not pull ASDF,
or one may @code
{
(require "asdf")
}
and that would implicitly require the former.
@item
@item
Please send us upstream any patches you make to ASDF itself,
Please send us upstream any patches you make to ASDF itself,
so we can merge them back in for the benefit of your users
so we can merge them back in for the benefit of your users
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment