[PD-cvs] pd/extra/pureunity README,1.1.2.1,1.1.2.2

Mathieu Bouchard matju at users.sourceforge.net
Fri Jun 1 18:31:56 CEST 2007


Update of /cvsroot/pure-data/pd/extra/pureunity
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11814

Modified Files:
      Tag: desiredata
	README 
Log Message:
.


Index: README
===================================================================
RCS file: /cvsroot/pure-data/pd/extra/pureunity/Attic/README,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -C2 -d -r1.1.2.1 -r1.1.2.2
*** README	5 Jan 2007 00:14:33 -0000	1.1.2.1
--- README	1 Jun 2007 16:31:54 -0000	1.1.2.2
***************
*** 74,78 ****
  SEVERITIES (in decreasing order)
  
!  * crash: Segmentation Fault, Bus Error, Illegal Instruction, Infinite Loop, 
     etc.  You can't deal with those errors at the level of the tests. Maybe there 
     should be a way to tell a test object to skip certain tests, by name, in 
--- 74,78 ----
  SEVERITIES (in decreasing order)
  
!  * crash: Segmentation Fault, Bus Error, Illegal Instruction, Infinite Loop,
     etc.  You can't deal with those errors at the level of the tests. Maybe there 
     should be a way to tell a test object to skip certain tests, by name, in 
***************
*** 87,91 ****
     those can't be handled by the test objects, so someone has to read them and 
     interpret them. Also they prevent test objects to ensure that error 
!    conditions produce error messages.
  
   * pd_error2(): I wish this would exist. It would be sort of like pd_error() 
--- 87,91 ----
     those can't be handled by the test objects, so someone has to read them and 
     interpret them. Also they prevent test objects to ensure that error 
!    conditions produce error messages. This includes stack overflow.
  
   * pd_error2(): I wish this would exist. It would be sort of like pd_error() 
***************
*** 191,196 ****
  
  FUTURE (from DesireData):
!   t   stringpointer
!   L   listpointer
    v   varpointer (instance symbol)
  
--- 191,195 ----
  
  FUTURE (from DesireData):
!   L   listpointer (still trying to figure out whether this will really happen)
    v   varpointer (instance symbol)
  
***************
*** 203,207 ****
    #f  grid of floats (float32)
    #d  grid of doubles (float64)
!   #r  grid of rubies (VALUE*)
  
  for a type prefix to be considered implemented, it has to
--- 202,206 ----
    #f  grid of floats (float32)
    #d  grid of doubles (float64)
!   #t  grid of Tcl_Object or t_atom or I don't know what.
  
  for a type prefix to be considered implemented, it has to
***************
*** 209,219 ****
  
    metaabstraction   for floats   for signals   for grids
!   [$1.inlet]         [inlet]      [inlet~]      [inlet]
!   [$1.outlet]       [outlet]     [outlet~]     [outlet]
!   [$1.do $2 $3]     [$2 $3]      [$2~ $3]      [# $2 $3]
!   [$1.taa]          [t a a]      noop          [t a a]
!   [$1.swap]         [swap]       noop          TODO
!   [$1.norm]         [abs]        [env~]        [# sq]->[#ravel]->[#fold +]->[#export]->[sqrt]
!   [$1.packunpack3]  pack,unpack  noop          TODO
  
  The first two cannot be implemented as abstractions and instead must be
--- 208,219 ----
  
    metaabstraction   for floats   for signals   for grids
!   [inlet.$1]         [inlet]      [inlet~]      [inlet]
!   [outlet.$1]       [outlet]     [outlet~]     [outlet]
!   [op2.$1 $2 $3]    [$2 $3]      [$2~ $3]      [# $2 $3]
!   [taa.$1]          [t a a]      noop          [t a a]
!   [swap.$1]         [swap]       noop          TODO
!   [norm.$1]         [abs]        [env~]        [# sq]->[#ravel]->[#fold +]->[#export]->[sqrt]
!   [packunpack3.$1]  pack,unpack  noop          TODO
!   [rand.$1]         ..................................
  
  The first two cannot be implemented as abstractions and instead must be
***************
*** 250,270 ****
  report any errors.
  
! (((To report errors and inaccuracies, output them through the properties outlet at the right. If there is no
! properties outlet in $foo (curently almost nothing in Pd has one),
! then $foo-rule must have one more outlet than $foo.)))
  
! (((Float messages coming out of the properties outlet of $foo-rule report
  accuracy. Named error messages come out with selector "error" followed by
! an error-symbol and then its arguments.)))
  
! (((In the case of true/false logic, a value of 0 means that a test has passed
  and a 1 means that a test has failed. Those values represent failure and not
  success. The reason is so that it matches with accuracy levels, where 0 is
  perfectly accurate, but any inaccuracy shows up as a relative error fraction.
  Any finite nonnegative value is allowed for accuracy, because it is expected
! to be the result of a norm))).
  
! (((In standard math, "Discrete Metric" is when there are only two possible
! distances between objects: together=0 and apart=1)))
  
  +-+-+--+---+-----+--------+-------------+---------------------+
--- 250,270 ----
  report any errors.
  
! To report errors and inaccuracies, output them through the properties outlet
! at the right. If there is no properties outlet in $foo (curently almost
! nothing in Pd has one), then $foo-rule must have one more outlet than $foo.
  
! Float messages coming out of the properties outlet of $foo-rule report
  accuracy. Named error messages come out with selector "error" followed by
! an error-symbol and then its arguments.
  
! In the case of true/false logic, a value of 0 means that a test has passed
  and a 1 means that a test has failed. Those values represent failure and not
  success. The reason is so that it matches with accuracy levels, where 0 is
  perfectly accurate, but any inaccuracy shows up as a relative error fraction.
  Any finite nonnegative value is allowed for accuracy, because it is expected
! to be the result of a norm.
  
! In standard math, "Discrete Metric" is when there are only two possible
! distances between objects: together=0 and apart=1
  
  +-+-+--+---+-----+--------+-------------+---------------------+
***************
*** 274,283 ****
  ETC
  
- 
  (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
--- 274,279 ----
***************
*** 608,609 ****
--- 604,624 ----
  
  +-+-+--+---+-----+--------+-------------+---------------------+
+ Old pre-DesireData ChangeLog for PureUnity:
+ 
+ version 0.0 (2006.01.06):
+  * LICENSE is GPL
+  * doc is in README
+  * new object classes:
+    * [commutator],   [commutative-test]
+    * [associator],   [associative-test]
+    * [invertor],      [invertible-test]
+    * [distributor], [distributive-test]
+    * [trichotomy-test], ...
+    * [twice], [3times], [4times], [^]
+    * [tree], [protocols-tree]
+    * [rtimer]
+    * for $1 in f,~ and some of #:
+      [$1.norm], [$1.taa], [$1.do], [$1.packunpack3], [$1.swap]
+      [$1.inlet], [$1.outlet]
+ 
+ +-+-+--+---+-----+--------+-------------+---------------------+





More information about the Pd-cvs mailing list