On 03/06/2011 08:22 PM, Julian Lamb wrote:
> 
>> As Stefan Tauner wrote:
>>
>>> skimmed over (the getopt code in) main() and was greeted by a creative
>>> variation of whitespace behavior (8-unit tabs + 4-unit spaces) :(
>> Well, there's nothing wrong with that per se.  Alas, there are other
>> functions apparently written with the assumption that one hard tab
>> occupies four columns, and in even other cases, there are four spaces
>> in front of the first tab. :/  Plus, a lot of trailing whitespace all
>> over the file.
> Welcome to communal software development!  When many different people 
> contribute, you're bound to get a mix.  Stefan's original code used a 
> "unique" indentation method (2 spaces to start, then +4 spaces for each 
> level afterward)...I'm assuming he was using some specific Emacs 
> modeline for his coding.

It should be 4 spaces per increment, never two anywhere what I know of.
Maybe in error? I use emacs with the following code snippet in my .emacs:
;;; Common C-mode hooks
(defun my-c-mode-hook ()
  (setq c-basic-offset 4)
  (turn-on-font-lock))
(add-hook 'c-mode-hook 'my-c-mode-hook)

Original emacs uses 2 and linux/BSD uses 8. This is something in between.

My original intentions for code standard are described in the HACKING
file of the repository.
(http://git.gpleda.org/?p=gerbv.git;a=blob;f=HACKING;h=a700f7bb6a280a5e38c69ea21829aed1add84bbe;hb=HEAD).

When I started to get contributions I was glad to get contributions and
did not enforce any coding standard.

Anyhow, I'm still more glad for all contributions than for code standard.

Regards,
/Stefan

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Gerbv-devel mailing list
Gerbv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gerbv-devel

Reply via email to