From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4487 invoked by alias); 13 Dec 2010 17:43:42 -0000 Received: (qmail 4475 invoked by uid 22791); 13 Dec 2010 17:43:41 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 13 Dec 2010 17:43:36 +0000 Received: (qmail 30473 invoked from network); 13 Dec 2010 17:43:34 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 13 Dec 2010 17:43:34 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.72) (envelope-from ) id 1PSCQv-0005kd-CW; Mon, 13 Dec 2010 17:43:33 +0000 Date: Mon, 13 Dec 2010 17:43:00 -0000 From: "Joseph S. Myers" To: Sebastian Pop cc: gcc@gcc.gnu.org Subject: Re: C/C++ extensions for array notations In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-12/txt/msg00338.txt.bz2 On Mon, 13 Dec 2010, Sebastian Pop wrote: > Hi, > > I would like to ask the opinion of C/C++ maintainers about the extension > that the Intel compiler proposes for array notations: > http://software.intel.com/sites/products/documentation/studio/composer/en-us/2011/compiler_c/index.htm#optaps/common/optaps_par_cean_prog.htm > > Are there strong opinions against this extension? I don't see any specification there at the language standard level of how this interacts with the type system, with sizeof (and C1X alignof and GNU typeof), with array-to-pointer decay, what the type compatibility rules are, what is a constraint violation and what is runtime undefined (regarding integer constant expression or non-i-c-e values being out of range or disagreeing within an expression, for example). Likewise regarding type conversions (implicit and otherwise). And regarding sequence point rules (use the terminology in C1X and C++0X in providing such a specification, please). -- Joseph S. Myers joseph@codesourcery.com