/[gzz]/gzz/doc/pegboard/coding_standard--vegai/peg.rst
ViewVC logotype

Diff of /gzz/doc/pegboard/coding_standard--vegai/peg.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.5 by Vegai, Thu Jan 9 17:22:26 2003 UTC revision 1.6 by tjl, Fri Jan 10 08:29:02 2003 UTC
# Line 12  PEG coding_standard--vegai: Coding Stand Line 12  PEG coding_standard--vegai: Coding Stand
12  Our coding standard (/gzz/CODING) requires revising, mainly because of the  Our coding standard (/gzz/CODING) requires revising, mainly because of the
13  large and growing amount of python code.  large and growing amount of python code.
14    
15    Issues
16    ======
17    
18    - our \*.java have the license attached to every file. Is that necessary?  
19    
20        RESOLVED: Yes, according to FSF.
21    
22    - should we have automatic tests for enforcing parts of the standard?
23    
24    - should the rcs id variable be "rcsid" or "rcsId" ?
25    
26    - should all code and data really be in classes? If so, why?
27    
28    - should Tabs be allowed or not?
29    
30  Changes  Changes
31  =======  =======
# Line 60  These apply to all \*.py (and possibly \ Line 74  These apply to all \*.py (and possibly \
74  10. Never use tabs.      10. Never use tabs.    
75    
76    
 Questions  
 =========  
   
 - our \*.java have the license attached to every file. Is that necessary?    
 - tests for enforcing parts of the standard?  
   
77    
78  Reference  Reference
79  =========  =========

Legend:
Removed from v.1.5  
changed lines
  Added in v.1.6

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26