[PD-cvs] abstractions/pureunity README,1.2,1.3

[Mathieu Bouchard]

Update of /cvsroot/pure-data/abstractions/pureunity
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv20468

Modified Files:
	README 
Log Message:
.


Index: README
===================================================================
RCS file: /cvsroot/pure-data/abstractions/pureunity/README,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** README	29 Dec 2005 18:47:56 -0000	1.2
--- README	29 Dec 2005 23:04:27 -0000	1.3
***************
*** 80,83 ****
--- 80,104 ----
  
  +-+-+--+---+-----+--------+-------------+---------------------+
+ PROTOCOL FOR [error]
+ 
+ new:
+   optional argument which would either be a float
+   (e.g. the $0 of the enclosing abstraction) or a pointer.
+ 
+ inlet 0:
+   set $scapegoat:
+     replaces the originator of the message by $scapegoat, which can be a
+     float or a pointer
+ 
+   error $1 ...:
+     causes its arguments to be concatenated, space-separated (may include
+     floats), and then sent through pd_error using the appropriate
+     originator (scapegoat).
+ 
+   list $1 ...:
+     for future use. would use pd_error2() (see README or previous mail).
+     $1 has to be a symbol.
+ 
+ +-+-+--+---+-----+--------+-------------+---------------------+
  ETC
  
***************
*** 85,86 ****
--- 106,121 ----
  (write me!)
  
+ 
+ 
+ 
+ If +-test.pd tests [+], it can test for hotness, coldness, it can test
+ that only one result is produced per hot message, that all results are
+ float, that a few example additions work, and that with random inputs it
+ respects commutativity, associativity, invertibility, within appropriate
+ relative-error bounds, etc.
+ 
+ However +-test.pd can't test that errormessages aren't printed during the
+ testing. This may be something that we want to check for, and currently
+ the best way to handle it is to search the console for error messages, and
+ if there are any, restart the tests in verbose mode and see where the
+ error happens exactly.