Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261705AbUKPMbT (ORCPT ); Tue, 16 Nov 2004 07:31:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261963AbUKPMbT (ORCPT ); Tue, 16 Nov 2004 07:31:19 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:4509 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S261705AbUKPMbQ (ORCPT ); Tue, 16 Nov 2004 07:31:16 -0500 Date: Tue, 16 Nov 2004 13:31:10 +0100 (MET) From: Jan Engelhardt To: Simon Braunschmidt cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] [Request for inclusion] Filesystem in Userspace In-Reply-To: <4199DDF2.5040700@corscience.de> Message-ID: References: <84144f0204111602136a9bbded@mail.gmail.com> <84144f020411160235616c529b@mail.gmail.com> <4199DDF2.5040700@corscience.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 799 Lines: 25 >> The have been >> patches to get rid of the existing casts so please don't introduce new >> ones. > >I vote for explicit casts, makes code more readable. And makes it more error prone. Once upon a time, a user wrote: ptr = (int *)malloc(...) And justified the use of the cast because gcc generated a warning, and I replied that if he'd included (yeah, user space), the warning would be gone, even without a cast. Sigh. Jan Engelhardt -- Gesellschaft für Wissenschaftliche Datenverarbeitung Am Fassberg, 37077 Göttingen, www.gwdg.de - 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/