[PD-cvs] pd/src rules.txt,1.1.2.1,1.1.2.2

[Mathieu Bouchard]

Update of /cvsroot/pure-data/pd/src
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21349

Modified Files:
      Tag: desiredata
	rules.txt 
Log Message:
.


Index: rules.txt
===================================================================
RCS file: /cvsroot/pure-data/pd/src/Attic/rules.txt,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -C2 -d -r1.1.2.1 -r1.1.2.2
*** rules.txt	12 Jul 2007 00:31:27 -0000	1.1.2.1
--- rules.txt	18 Jul 2007 04:18:00 -0000	1.1.2.2
***************
*** 10,14 ****
  
  #003: Accessing an object's privates directly, is likely to cause trouble in the future. All @variables are private, but
!       methods may also be marked as private or protected, by a visible comment where the definition is.
  
  #004: Indentation is whatever you like as long as it's locally consistent. Tab stops (of the tab key) are at multiples of 8,
--- 10,15 ----
  
  #003: Accessing an object's privates directly, is likely to cause trouble in the future. All @variables are private, but
!       methods may also be marked as private or protected, by a visible comment where the definition is. (C++ variables are
!       not necessarily like that, mostly because of compatibility with classic pd)
  
  #004: Indentation is whatever you like as long as it's locally consistent. Tab stops (of the tab key) are at multiples of 8,
***************
*** 16,20 ****
        own line, but close-braces do, at least because of how the diff program works.
  
! #005: Screen width is assumed to be about 132 characters, not 80. This is especially useful for cutting down the need
        to wrap lines. Newlines that have to do with linewrap get confused with meaningful newlines. Blank lines should be
        used sparsely: the more there are blank lines, the less meaningful they are. If you want blank lines everywhere,
--- 17,21 ----
        own line, but close-braces do, at least because of how the diff program works.
  
! #005: Screen width is assumed to be about 125 characters, not 80. This is especially useful for cutting down the need
        to wrap lines. Newlines that have to do with linewrap get confused with meaningful newlines. Blank lines should be
        used sparsely: the more there are blank lines, the less meaningful they are. If you want blank lines everywhere,
***************
*** 26,44 ****
          for (int i=0; i<noutlets; i++) x->outlets[i]->name = gensprintf("outlet #%d",i);
  
! #007:
  
! #008:
  
  #009:
  
  #010:
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
--- 27,41 ----
          for (int i=0; i<noutlets; i++) x->outlets[i]->name = gensprintf("outlet #%d",i);
  
! #007(Tcl): an attribute is a reader method named like "some_noun", which has no args and returns a value and/or a writer
!       method named like "some_noun=", which takes one arg (or more?) and returns no value. Together they are seen as
!       manipulating a variable. If the variable directly exists in the object, it should be called "@some_noun". The "="
!       suffix should be only used for that purpose. (we should think about whether to accept multiple args, because other
!       languages with a similar concept only allow one arg in the writer)
  
! #008(Tcl): Nouns like "visibility" that are simpler as adjectives and whose main purpose is to return a yes/no value, can
!       be named like "visible?" and are declined in the same way, e.g. "visible?=" and "@visible?". The "?" suffix should be
!       only used for that purpose.
  
  #009:
  
  #010: