Design By Contract

ruby-talk
1

Several months ago, I made a posting regarding a possible enhancement to
Ruby to facilitate Design by Contract (DbC). Matz and Justin were kind
enough to reply w/their thoughts and I was curious to know whether there is
any hope for such functionality in any near future release of Ruby.

Hello ken,

I dont know if there are any upcoming plans for this,
so will defer on that thought. The obvious idea though
is why not make a class with a method called 'contract’
and then use mixin’s to add the method(s) into whichever
class is going to be talking to the client (or other
class etc). This may be a ‘poormans’ version of 'DbC’
but its implementable right now :slight_smile:

Design by contract always seems to be (at least in my
eyes) something thats very helpful for programs which
dont deal with ‘external’ applications or clients. If
your using design by contract to ~replace~ SEDLC
(Software Engineering Development Life Cycles) then I
think your coming at it from the ‘wrong’ approach.

anyway, i dont want to start a flamewar, so thats my
2cents as it were.

regards
Stef

2

Hello Stef,

have you ever done “Design by contract”. I’m working with eiffel 8
hours a day, 6 days a week for 3 years now and i must say its a really
good tool and perfect if combined with extreme programming.

It just mean: Sit down and think and define the interface precisely.