good evening;
i have reformulated the test cases and run them through several
implementations.[0]
1. i had thought (eg. [1]) that abcl and asdf were compatible. is
there some special version involved? the cl.net release failed to
load.[2]
2. the description of the interaction between a
On 2010-03-09, at 19:00 , james anderson wrote:
good evening;
i have reformulated the test cases and run them through several
implementations.[0]
i have pushed these tot eh asdf-x repository[1] in case anyone wants
to suggest changes.
---
[1] :
On 3/9/10 Mar 9 -5:49 PM, Faré wrote:
Yes, it hasn't been documented so far. My bad. At least it now has a
well-defined meaning, as opposed to the previous mess.
a- when the source-file-type of a component is NIL, then the file type
is read from the last /-separated component of the string as
On 3/9/10 Mar 9 -5:49 PM, Faré wrote:
Dear James,
i have reformulated the test cases and run them through several
implementations.[0]
Thanks a lot!
1. i had thought (eg. [1]) that abcl and asdf were compatible. is
there some special version involved? the cl.net release failed to
b- when the source-file-type of a component is a string, then it will
be the type, and the last /-separated component of the string provides
the name.
This case worries me. It seems to require that every system definer
have a strongish sense of the internals of ASDF, and will give odd
On 3/9/10 Mar 9 -9:46 PM, Faré wrote:
b- when the source-file-type of a component is a string, then it will
be the type, and the last /-separated component of the string provides
the name.
This case worries me. It seems to require that every system definer
have a strongish sense of the
Sure. Or if you like you can also outline it in text and I will
translate. Whatever works. Cheers.
On Mar 9, 2010, at 22:39, Faré fah...@gmail.com wrote:
I can't find my way through the texinfo documentation. Too much
manual
section management. Could we be using something nicer? ReST?
