RE: [colorforth] Forth and XP
- Subject: RE: [colorforth] Forth and XP
- From: Fréderic DUBOIS <frederic.dubois@xxxxxxxxxxxxx>
- Date: Thu, 19 Jun 2003 13:47:24 +0200
> -----Message d'origine-----
> De : Samuel Falvo [mailto:falvosa@xxxxxxxxx]
> Envoyé : jeu. 19 juin 2003 08:05
> À : colorforth@xxxxxxxxxxxxxxxxxx
> Objet : [colorforth] Forth and XP
>
>
> I changed the subject again in case anyone would want to explore the
> relationships between Forth and Jazz as distinct from
> exploring extreme
> programming.
>
> > http://www.rolemodelsoftware.com/process/whatIsXp.php
> >
> > Do you have any pointers to or examples of
> >
> > A client's requirements, and those requirements are
> expressed as tests?
> >
> > I will continue reading in hops of discovering the above.
>
> I will get back to you on this, as I've just returned from an
> absolutely
> *outstanding* night of aikido. Very aerobic, very
> intellectual, and very
> tiring. :)
>
> I checked that site out, and that has got to be one of the best short
> introductions to what XP is that I've ever seen. Thanks for
> the link! :)
>
> --
> Samuel A. Falvo II
>
I encourage you to do so. I took a quick look; XP matches two of my favorite
words: simplicity and factoring.
I would like to reformulate a question by Mark: how do you make sure that
your tests cover all possible cases?
For instance, I'm currently writing an inference engine. It takes as input a
formula ( say, F->F) and it must answer yes if it is a theorem ( crash
otherwize :), and give it's demonstration. Here is more or less the spec.
How do you write tests for it?
Amicalement,
Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
Main web page - http://www.colorforth.com