RE: Swapping isa's (was Re: Hex Edit controls (resknife))

FROM : Jeff Laing
DATE : Wed Dec 01 23:28:44 2004

> On Nov 30, 2004, at 2:51 PM, Jeff Laing wrote:
> > There is no auditabiliy whatsoever, and those of us who actually *live*

by
> > code review will tell you that thats a recipe for disaster,
> > always, no exceptions.
>
> You can use a unit testing framework to create unit tests that verify
> your nib gets wired up properly on load.  This is one way of making
> sure that as you work, everything gets set up the way you want it (if
> you write the tests first) and stays that way as you modify things.


Without wanting to sound too negative, especially since the initial problem
seems to be with my machine and not with Interface Builder, you may well
have missed the point.

All thats happened is that you've pushed the audit capability out into the
test suite - I'd have to eyeball the test suite to ensure that it hit every
nib connection that needed testing, and I don't have any provable way of
knowing that my test coverage is complete. Whats out there in the nib is
opaque, you can't easily (1) read it directly to determine what tests are
necessary.

In effect, you'd have to replicate in code all the connections you expect to
be present in the nib, and if you've done that, why not just create them
with code in the first place and be done with it?

Jeff.

(1) I *am* going to look at what nibtool -a can tell me, and I suspect that
it may well fit the bill.