On Fri, Mar 19, 2010 at 3:42 AM, Robert Goldman rpgold...@sift.info wrote:
Juanjo --- do you have what you need to make asdf-ecl.lisp work again
(wrt traverse)? Is there anything we (I) can do to help with this?
I am still waiting to get see whether the package changes are fixed -- I
messed
Thansk for the latest changes, they work like a charm now.
I have done something which I do not know whether it is a desired protocol.
Namely I have submitted patches for asdf-ecl.lisp using launchpad.
I did this because I always found it more convenient to have a look at the
ECL bug/patch
On 19 March 2010 13:34, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
Thansk for the latest changes, they work like a charm now.
Glad to know it was just a package problem, and thanks to Robert
for the diagnostic and to you for the explanation!
I'm glad it didn't require
On Fri, Mar 19, 2010 at 7:51 PM, Faré fah...@gmail.com wrote:
Can you help with the configuration on Windows?
What is the ECL equivalent of LispWorks' get-folder-path?
Or if there isn't one builtin, how do I read a string entry from
the registry?
We do not export in ECL any way to read the
would it be possible to also add a version 3 milestone so that we
could explicitly push stuff /out/ of version 2?
Right now it seems like there's no way of telling the difference between
unmilestoned and milestoned out of version 2.
But my ignorance of launchpad is near complete, so it is
* README should say how to build the manual
* That said, how is the user supposed to build the manual?
There does not seem to be any rule for it in the Makefile.
* texipdf asdf.texinfo resulted in an error; an asdf.pdf was produced
nontheless. See PS for transcript.
* the manual should
In a system such as
(defsystem :foo
:component ((:file foo)))
where foo.lsp exists and is recognized by the lisp implementation as a valid
source file (ECL), ASDF imposes the file extension lisp. Furthermore,
adding our own extension
(defsystem :foo
:component ((:file foo.lsp)))
does not
On 20 March 2010 01:02, Robert Goldman rpgold...@sift.info wrote:
The manual does not build to hardcopy using TeX right now because it has
some ampersands in it that confuse TeX. Googling has not revealed to me
how to escape an `'.
Put this into the @ifnottex secttion, and use @key, etc.
@c
