this seems to be the modernized version of it:
https://github.com/brynbellomy/ObjC-DesignByContract
On 22 Jan 2014, at 12:37, Jens Alfke wrote:
On Jan 22, 2014, at 8:03 AM, jonat...@mugginsoft.com wrote:
I know there are some macros available,
http://www.roard.com/contracts/, but I haven’t
On 22 Jan 2014, at 17:50, Herman Chan wrote:
> this seems to be the modernized version of it:
> https://github.com/brynbellomy/ObjC-DesignByContract
This is indeed a later implementation.
It uses a metamacro approach as used in ReactiveCocoa.
The code also has dependencies on another library tha
On Jan 22, 2014, at 8:03 AM, jonat...@mugginsoft.com wrote:
> I know there are some macros available, http://www.roard.com/contracts/, but
> I haven’t experimented further as yet
Interesting. I like the idea of dynamically creating a subclass that wraps the
methods to be checked, but I don't
Does anyone regularly use design by contract in their Cocoa apps?
At present I often make use of NSAssert() et al to validate method inputs as a
passing nod to design by contract, but that’s it.
I know there are some macros available, http://www.roard.com/contracts/, but I
haven’t experimente
