[PD-dev] unit tests!

Tim Blechmann TimBlechmann at gmx.net
Fri Dec 30 00:31:23 CET 2005


> > >  * failure: a test object reports a problem through outlet 0.
> > how do you want it to be implemented? one object per patch, per
> > canvas (like switch~) or globally?
> 
> I don't understand your question, but then maybe you misread
> something or that I miswrote something.
> 
> Test objects only test what they can.

ah, sorry, i misunderstood your mail ...

> > i'd also suggest the addition of an assert object, that's similar
> > to my external on the cvs...
> 
> ok, I think that given what yours do, it should be called [error].
> Also it should take an optional argument which would either be a
> float (e.g.  the $0 of the enclosing abstraction) or a pointer. It
> would have one inlet, no outlet, and support the following messages:

i intended assert to be an object without overhead... but i also like
your generalisation. 
the only problem i see is, that i'd like to switch off the runtime
overhead in performance mode and check the asserts only in debug mode,
which would be either a canvas property or a global property ...
(unfortunately this distinction doesn't really exist in pd)

tim

-- 
mailto:TimBlechmann at gmx.de    ICQ: 96771783
http://www.mokabar.tk

You can play a shoestring if you're sincere
  John Coltrane
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20051229/a89e2c26/attachment.pgp>


More information about the Pd-dev mailing list