Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754742Ab3G3Qaw (ORCPT ); Tue, 30 Jul 2013 12:30:52 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:34182 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752625Ab3G3Qau (ORCPT ); Tue, 30 Jul 2013 12:30:50 -0400 Message-ID: <51F7EA35.6070501@wwwdotorg.org> Date: Tue, 30 Jul 2013 10:30:45 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: "jonsmirl@gmail.com" CC: David Gibson , James Bottomley , Grant Likely , Mark Rutland , "devicetree@vger.kernel.org" , "ksummit-2013-discuss@lists.linuxfoundation.org" , Russell King - ARM Linux , Ian Campbell , Pawel Moll , "linux-kernel@vger.kernel.org" , Richard Cochran , Tomasz Figa , "rob.herring@calxeda.com" , Domenico Andreoli , Jason Gunthorpe , Dave P Martin , "linux-arm-kernel@lists.infradead.org" Subject: Re: [Ksummit-2013-discuss] DT bindings as ABI [was: Do we have people interested in device tree janitoring / cleanup?] References: <20130725175702.GC22291@e106331-lin.cambridge.arm.com> <2007664.vYsECFSKrV@flatron> <51F39FD8.6080808@broadcom.com> <2460092.aLmjrOVh1g@flatron> <51F3A82E.2000907@broadcom.com> <1374988276.1973.29.camel@dabdike> <20130730014453.GJ29970@voom.fritz.box> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1006 Lines: 21 On 07/29/2013 08:15 PM, jonsmirl@gmail.com wrote: > On Mon, Jul 29, 2013 at 9:44 PM, David Gibson > wrote: ... >> I also think we should consider the option of having a simple and >> straightforward schema language which handles, say, 80% of cases with >> a fall back to C for the 20% of curly cases. That might actually be >> simpler to work with in practice than a schema language which can >> express absolutely anything, at the cost of being awkward for simple >> cases or difficult to get your head around. > > Would C++ work? You can use operating overloading and templates to > change the syntax into something that doesn't even resemble C any > more. >From my perspective, that's precisely why C++ should /not/ be used. -- 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/