From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267067AbUBMPmQ (ORCPT ); Fri, 13 Feb 2004 10:42:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267073AbUBMPmP (ORCPT ); Fri, 13 Feb 2004 10:42:15 -0500 Received: from denise.shiny.it ([194.20.232.1]:12501 "EHLO denise.shiny.it") by vger.kernel.org with ESMTP id S267067AbUBMPmK (ORCPT ); Fri, 13 Feb 2004 10:42:10 -0500 Message-ID: X-Mailer: XFMail 1.4.7 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040213153542.29686f0f.buffer@antifork.org> Date: Fri, 13 Feb 2004 16:42:04 +0100 (CET) From: Giuliano Pochini To: "Angelo Dell'Aera" Subject: Re: PATCH, RFC: 2.6 Documentation/Codingstyle Cc: Linux-Kernel Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 13-Feb-2004 Angelo Dell'Aera wrote: >>Deeply nested doesn't mean unreadable or badly structured. > > I think you're really wrong since "deeply nested" means exactly "unreadable > and badly structured" and you could easily realize it by simply spending ~10 > hours per day coding and/or taking a look at the code written by someone > which is not you. Deeply means 4-5 levels in this case, not 20. The example I posted was only 3 (plus the one of the function) levels down. -- Giuliano.