Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55240C2C.2020603@mailbox.org>
Date: Tue, 07 Apr 2015 18:56:12 +0200
From: Frank Dittrich <frank.dittrich@...lbox.org>
To: john-dev@...ts.openwall.com
Subject: Re: Coding Style

On 04/07/2015 06:01 PM, magnum wrote:
> On 2015-04-07 14:45, Kai Zhao wrote:
>> Do you prepare to kill the rule "tab for indent, space for align" ?
> 
> On the contrary I said I'm prepared to kill FOR it. Not literally of
> course - if it turns out I'm the only one here that understands the
> beauty of "tab for indent, space for align", I can live with not
> aligning at all (that is, just indenting one (1) more level).

Not sure it matters, because others contribute more than I do, but I
also prefer tabs for indentation and spaces for alignment.
And I really got used to the editor's default tab width of 8.

Regarding line size: I can easily live with 132. 80 is better if you
want to print longer source codes on paper for some reason.
Please avoid splitting stdout or stderr strings to reduce the line size.
It makes  grepping just too error prone.

Frank

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.