3 CodingStyle - standards while programming for LilyPond
7 Please use these standards while doing programming for LilyPond
9 Functions and methods do not return errorcodes, but use assert for
14 A program should be light and agile, its subroutines
15 connected like a strings of pearls. The spirit and intent of
16 the program should be retained throughout. There should be
17 neither too little nor too much, neither needless loops nor
18 useless variables, neither lack of structure nor overwhelming
21 A program should follow the 'Law of Least
22 Astonishment'. What is this law? It is simply that the
23 program should always respond to the user in the way that
26 A program, no matter how complex, should act as a
27 single unit. The program should be directed by the logic
28 within rather than by outward appearances.
30 If the program fails in these requirements, it will be
31 in a state of disorder and confusion. The only way to correct
32 this is to rewrite the program.
34 -- Geoffrey James, "The Tao of Programming"
38 Definitions of classes that are only accessed via pointers
39 (*) or references (&) shall not be included as include files.
41 Include files in C++ always have the file name extension ".hh".
43 Implementation files in C++ always have the file name
46 Inline definition files always have the file name extension ".icc".
48 Template include files always have the file name extension ".tcc".
56 (add-hook 'c-mode-hook
57 '(lambda ()(setq c-basic-offset 4)))
60 (add-hook 'c++-mode-hook
61 '(lambda() (c-set-style "Stroustrup")
66 =head2 CLASSES and TYPES:
69 AClass_name (for Abbreviation_class_name)
74 Type Class::member_type_
76 the C<type> is a Hungarian notation postfix for C<Type>. See below
81 The source is commented in the DOC++ style. Check out doc++ at
82 http://www.zib.de/Visual/software/doc++/index.html
85 C style comments for multiline comments.
92 Long class documentation.
105 short memo. long doco of member()
106 @param description of arguments
109 Rettype member(Argtype);
115 Unfortunately most of the code isn't really documented that good.
118 =head2 CLASSNAMES (2)
120 A lot of classes in LilyPond start with 'P', this is to distinguish
121 certain parts of LilyPond: the P stands for Printer, and the P-classes
122 are supposed to be more lowlevel than the others. Example:
124 Staff uses PStaff, PScore and PCol to do the typesetting of
125 symbols. Staff is the "brains" for PStaff
127 NB: in PCursor (which is part of the library) P stands for PointerCursor
134 ///check that *this satisfies its invariants, abort if not.
137 /// print *this (and substructures) to debugging log
141 protected member. Usually invoked by non-virtual XXXX()
145 /**add some data to *this.
146 Presence of these methods usually imply that it is not feasible to this
151 /// replace some data of *this
154 =head1 HUNGARIAN NOTATION NAMING CONVENTION
156 Proposed is a naming convention derived from the so-called I<Hungarian
161 The Hungarian Notation was conceived by or at least got its name from,
162 the hungarian programmer Charles Simonyi. It is a naming convention
163 with the aim to make code more readable (for fellow programmers), and
164 more accessible for programmers that are new to a project.
166 The essence of the Hungarian Notation is that every identifier has a
167 part which identifies its type (for functions this is the result
168 type). This is particularly useful in object oriented programming,
169 where a particular object implies a specific interface (a set of
170 member functions, perhaps some redefined operators), and for
171 accounting heap allocated memory pointers and links.
175 Another fun quote from Microsoft Secrets:
178 The Hungarian naming convention gives developers the ability
179 to read other people's code relatively easily, with a minmum
180 number of comments in the source code. Jon De Vann estimated
181 that only about 1 percent of all lines in the Excel product
182 code consist of comments, but the code is still very
183 understandable due to the use of Hungarian: "if you look at
184 our source code, you also notice very few comments. Hungarian
185 gives us the ability to go in and read code..."
188 Wow! If you use Hungarian you don't have to document your software!
189 Just think of the hours I have wasted documenting while this "silver bullet"
190 existed. I feel so stupid and ashamed!
198 more keystrokes (disk space!)
202 it looks silly C<get_slu_p()>
206 it looks like code from micro suckers
210 (which) might scare away some (otherwise good?)
211 progammers, or make you a paria in the free
220 not very useful if not used consistently
224 usefullness in I<very large>
225 (but how many classes is very large?)
238 learn about cut and paste / use emacs or vi
239 or lean to type using ten fingers
243 Use emacs dabbrev-expand, with dabbrev-case-fold-search set to nil.
247 use no, or pick less silly, abbrvs.
251 use non-ambiguous postfixes C<identifier_name_type_modifier[_modifier]>
254 Macros, C<enum>s and C<const>s are all uppercase,
255 with the parts of the names separated by underscores.
264 unsigned char. (The postfix _by is ambiguous)
293 Zero terminated c string
301 =head2 User defined types
308 Slur* slur_p = new Slur;
312 The following types modify the meaning of the prefix.
313 These are precede the prefixes:
327 const. Note that the proper order C<Type const> i.s.o. C<const Type>
331 A const pointer. This would be equivalent to C<_c_l>, but since any
332 "const" pointer has to be a link (you can't delete a const pointer),
337 temporary pointer to object (link)
341 pointer to newed object
353 Variable loop: an integer
357 Temporary variable: an unsigned integer
361 Variable test: a character
363 =item C<first_name_str>
365 Variable first_name: a String class object
367 =item C<last_name_ch_a>
369 Variable last_name: a C<char> array
373 Variable foo: an C<Int*> that you must delete
377 Variable bar: an C<Int*> that you must not delete