- 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