Results of 0 - 1 of about 0 (0.000 sec.)
- Coding Standards for GNUstep Libraries: 2. ChangeLog Entries
- @digest: 984bebae35e19abf82c39a6d2a0bd6c5
- @id: 63450
- @mdate: 2015-08-31T02:18:26Z
- @size: 5205
- @type: text/html
- content-type: text/html; charset=utf-8
- description: Coding Standards for GNUstep Libraries: 2. ChangeLog Entries
- distribution: global
- generator: texi2html 1.82
- keywords: Coding Standards for GNUstep Libraries: 2. ChangeLog Entries
- resource-type: document
- #keywords: nsslider (8108), initwithframe (3694), fedor (2817), changelog (2114), adam (726), wrapping (602), entries (567), december (361), gnustep (339), formats (267), changed (249), texi2html (248), changes (216), methods (194), someone (187), although (180), typically (166), comments (144), appropriate (139), look (128), currently (128), standards (116), similar (116), important (114), directories (112), multiple (110), libraries (107), contents (101), current (69), directory (64), document (62), documentation (58)
- [ < ] [ > ] [ << ] [ Up ] [ >> ] [ Top ] [Contents] [Index] [ ? ] 2. ChangeLog Entries Always include a ChangeLog entry for work that you do. Look for the ChangeLog file in the current directory or look up to any number of parent directories. Typically there is one for each library. Emacs currently formats the header like this: 2000-03-11 Adam Fedor <fedor@gnu.org> and formats changes to functions/methods like this: * Source/NSSlider.m ([NSSlider -initWithFrame:]): to which you add your own comments on the same line (with word wrapping). Although if you're making similar changes to multiple methods, it's ok to leave out the function/method name. Important: Changelog entries should state what was changed, not why it was changed. It's more appropriate to put that in the source code, where someone can find it, or in the documentation. [ << ] [ >> ] [ Top ] [Contents] [Index] [ ? ] This document was generated by Adam Fedor on December 24, 2013 using texi2html 1.82 .
...
-
http://www.gnu.org/savannah-checkouts/gnu/gnustep/resources/documentation/Developer/CodingStandards/coding-standards_2.html
- [detail]
- [similar]
PREV
NEXT