Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 31 Dec 2002 00:20:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 31 Dec 2002 00:20:15 -0500 Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:14431 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Tue, 31 Dec 2002 00:20:14 -0500 Date: Tue, 31 Dec 2002 00:28:37 -0500 From: Pete Zaitcev Message-Id: <200212310528.gBV5Sbn29105@devserv.devel.redhat.com> To: "Emiliano Gabrielli" cc: linux-kernel@vger.kernel.org Subject: Re: Indention - why spaces? In-Reply-To: References: <20021230122857.GG10971@wiggy.net> <200212301249.gBUCnXrV001099@darkstar.example.net> <20021230131725.GA16072@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 831 Lines: 23 > IMHO and in my personal projects I use the following indenting rules: > > 1) use TABs for _indentation_ > 2) use SPACEs for aligning > > here is an exaple: > >if (cond) { >dosometing; >printf("This is foo: '%s', and this bar: '%d'", > foo, bar); BTW, this practice is codified in Solaris developer's guidelines. They even have a perl script called "hdrchk" which is run before commits and tells about violations. Actually, the Sun requirement is to have exactly 4 spaces, but it sounds a little too anal to me. -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/