rfc: indenting and coding style

[William Hubbs]

Hello Hynek,

On Mon, Dec 20, 2010 at 11:23:00AM +0100, Hynek Hanke wrote:
> On 20.12.2010 01:51, William Hubbs wrote:
> 2. A single level of indentation is 4 spaces. Tab characters
> must not be present in the code.
 
 Please use a tab as a level of indentation. That way, people can adjust
 the tab width to be whatever they want without affecting the
 indentation levels.

> 4. Function names should be
>      a. lowercase words separated by underscores
>      b. functions which are only implementation details of the given
>         source file should be declared as static
>      c. names of all other functions in a file should start with
>         a prefix specific to that file (generally the filename
>         without suffix)
 
 I don't agree with C here. Suppose that a file gets renamed or a
 function gets moved to another file. Now we have to rename the function
 as well as adjust all calls to the function.
William

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20101220/a004650c/attachment.pgp>