| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <47C5CFEF.8020402@student.ltu.se> Date: Wed, 27 Feb 2008 22:02:39 +0100 From: Richard Knutsson <ricknu-0@...dent.ltu.se> To: Benny Halevy <bhalevy@...asas.com> CC: Randy Dunlap <randy.dunlap@...cle.com>, khc@...waw.pl, bhalevy.lists@...il.com, jengelh@...putergmbh.de, linux-kernel@...r.kernel.org Subject: Re: [RFC] CodeStyle: Use spaces when aligning/decorating Benny Halevy wrote: > > How about this: > > -Tabs are 8 characters, and thus indentations are also 8 characters. > -There are heretic movements that try to make indentations 4 (or even 2!) > -characters deep, and that is akin to trying to define the value of PI to > -be 3. > +Tabs are used for logical indentation, e.g., code is indented with > +a number of tabs equal to its nesting level. From there on, > +use space characters for decorative indentation. This method > +is agnostic to the editor's tab-expansion settings. > +That said, expanding tabs to a small number of spaces (4, or even 2!) encourages > +excessive nesting and resulting over-complexity; that is akin to trying to define > +the value of PI to be 3. Therefore, tabs are always assumed to be 8 characters-wide. > > Not sure about the PI-reference in that context, but the rest IMO looks good. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists