Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757320AbXHBNgJ (ORCPT ); Thu, 2 Aug 2007 09:36:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752650AbXHBNf5 (ORCPT ); Thu, 2 Aug 2007 09:35:57 -0400 Received: from sovereign.computergmbh.de ([85.214.69.204]:54461 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751942AbXHBNf5 (ORCPT ); Thu, 2 Aug 2007 09:35:57 -0400 Date: Thu, 2 Aug 2007 15:35:56 +0200 (CEST) From: Jan Engelhardt To: Miklos Szeredi cc: adobriyan@gmail.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, torvalds@linux-foundation.org Subject: Re: [PATCH] type safe allocator In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 808 Lines: 26 On Aug 2 2007 15:06, Miklos Szeredi wrote: >> On Aug 2 2007 16:04, Alexey Dobriyan wrote: >> >On 8/2/07, Miklos Szeredi wrote: >> >> fooptr = kmalloc(sizeof(struct foo), ...); >> > >> >Key word is "traditional". Good traditional form which even half-competent >> >C programmers immediately parse in retina. >> >> And being aware of the potential type-unsafety makes programmers more >> careful IMHO. > >That's a _really_ good reason ;) Yes, a good reason not to use g_new(), so people do get bitten when they are doingitwrong. Jan -- - 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/