Thanks Daniel,
I'll set up a list and the hooks.
On Oct 6, 2009, at 10:17 PM, Daniel Herring wrote:
> On Tue, 6 Oct 2009, Nikodemus Siivola wrote:
>
>> 2009/10/6 Attila Lendvai :
>>
>>> how about an atom feed of the commit log? it's available at the
>>> bottom
>>
>> I'd prefer email, because
On Tue, 6 Oct 2009, Nikodemus Siivola wrote:
> 2009/10/6 Attila Lendvai :
>
>> how about an atom feed of the commit log? it's available at the bottom
>
> I'd prefer email, because that makes it easy to comment on stuff. Feed
> is better than nothing, of course.
It is not terribly hard to have an
>> when test-op'ed, we print the result object to *standard-output*. when
>> used interactively, the test defun that was used to start the testing
>> simply returns the result value which we inspect in slime when needed.
>>
>
> Do you see the same problems I see? I find that my test's output can
>
Attila Lendvai wrote:
>> That is why I have been suggesting that we provide a test operation that
>> binds a stream --- because most of the test frameworks I have worked
>> with provide a test report, rather than returning results.
>
> fyi, stefil returns a CLOS object containing the test results
2009/10/6 Attila Lendvai :
> how about an atom feed of the commit log? it's available at the bottom
I'd prefer email, because that makes it easy to comment on stuff. Feed
is better than nothing, of course.
Cheers,
-- Nikodemus
___
asdf-devel mailing
> Do we have these? If not, can we get them?
how about an atom feed of the commit log? it's available at the bottom
of the gitweb page:
http://common-lisp.net/gitweb?p=projects/asdf/asdf.git
i have many repos among my feeds in google reader, it's a very
convenient way to follow what's happening o
Do we have these? If not, can we get them?
Cheers,
-- Nikodemus
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
2009/10/5 Robert Goldman :
> Recently, we modified the default dependencies of the test-op, entirely
> reasonably, so that by default you need to do a load-op on a system
> before doing the test-op. Unfortunately, this means that system
> definitions written for new ASDF will not test-op properly
> That is why I have been suggesting that we provide a test operation that
> binds a stream --- because most of the test frameworks I have worked
> with provide a test report, rather than returning results.
fyi, stefil returns a CLOS object containing the test results (and
provides slime inspector
