Mercurial > pylearn
comparison doc/v2_planning/API_coding_style.txt @ 1178:10bc5ebb5823
coding_style: Added note about the need to provide guidelines for serialization-friendly code
| author | Olivier Delalleau <delallea@iro> |
|---|---|
| date | Fri, 17 Sep 2010 16:21:55 -0400 |
| parents | 53340a8df1fa |
| children | 67f4edabb0cc |
comparison
equal
deleted
inserted
replaced
| 1171:fab72f424ee0 | 1178:10bc5ebb5823 |
|---|---|
| 515 Things still missing from this document, being discussed in coding_style.txt: | 515 Things still missing from this document, being discussed in coding_style.txt: |
| 516 - Proper style for C code and Mercurial commits | 516 - Proper style for C code and Mercurial commits |
| 517 - Enforcing 100% test coverage of the code base | 517 - Enforcing 100% test coverage of the code base |
| 518 - Providing ways to add type checking for function arguments | 518 - Providing ways to add type checking for function arguments |
| 519 - Conventions for script usage documentation and argument parsing | 519 - Conventions for script usage documentation and argument parsing |
| 520 | 520 - Conventions for class / method / function documentation |
| 521 - Guidelines for serialization-friendly code (hint: nested and lambda | |
| 522 functions, as well as instance methods, cannot be serialized, and | |
| 523 apparently there are some issues with decorators -- to be investigated). | |
| 524 | |
| 525 |