[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Re: Integrating unit tests into source code
From: |
felix winkelmann |
Subject: |
Re: [Chicken-users] Re: Integrating unit tests into source code |
Date: |
Fri, 15 Dec 2006 09:50:28 +0100 |
On 12/15/06, Peter Bex <address@hidden> wrote:
I suppose we just have to agree to disagree on this issue. Maybe a user
poll about what approach to take is in order?
Why can't everybody just use the approach he/she prefers? When asking
about the "docsexpr" thingy on this list, I was just trying to figure out what
users generally think of it. I will add some sort of generalized approach
to add "annotations" based on a quoted list/docstring to chicken, what
people make from that is their own choice.
I agree that too much tests in the body of a procedure might distract, though.
I also find contracts interesting, but didn't understand the particular way
PLT handles it, yet.
cheers,
felix
Re: [Chicken-users] Integrating unit tests into source code, Michele Simionato, 2006/12/14
Re: [Chicken-users] Integrating unit tests into source code, Peter Busser, 2006/12/14
- Re: [Chicken-users] Integrating unit tests into source code, Peter Bex, 2006/12/14
- Re: [Chicken-users] Re: Integrating unit tests into source code, Brandon J. Van Every, 2006/12/15
- Re: [Chicken-users] Re: Integrating unit tests into source code, Thomas Christian Chust, 2006/12/15
- Re: [Chicken-users] Re: Integrating unit tests into source code, Brandon J. Van Every, 2006/12/15
- Re: [Chicken-users] Re: Integrating unit tests into source code, Thomas Christian Chust, 2006/12/15
Re: [Chicken-users] Integrating unit tests into source code, Kon Lovett, 2006/12/14