From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3487 invoked by alias); 11 Feb 2015 08:44:01 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 3468 invoked by uid 89); 11 Feb 2015 08:44:01 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 11 Feb 2015 08:44:00 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id A32291164F0; Wed, 11 Feb 2015 03:43:58 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id L-SlXi1YWWcs; Wed, 11 Feb 2015 03:43:58 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3336811646F; Wed, 11 Feb 2015 03:43:58 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 5C3E640EAD; Wed, 11 Feb 2015 12:43:54 +0400 (RET) Date: Wed, 11 Feb 2015 08:44:00 -0000 From: Joel Brobecker To: Doug Evans Cc: Keven Boell , gdb-patches Subject: Re: [V4 01/18] vla: introduce allocated/associated flags Message-ID: <20150211084354.GK4738@adacore.com> References: <1421243390-24015-1-git-send-email-keven.boell@intel.com> <1421243390-24015-2-git-send-email-keven.boell@intel.com> <20150209065213.GA15579@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2015-02/txt/msg00293.txt.bz2 > I can even imagine removing data_location from the main_type "base class" > [see below]. But I'm not advocating that that needs to be done > now or even soon. I thought of that, also, and in the end, decided not to suggest it because it is slightly more complex to implement. In particular, you'd need to know whether you'll neex some extra room at the end before you allocate the type (or else, you'll have to realloc it later on, and this might not be easy to do when it is allocated on an obstack). There were also minor difficulties associated to debugging and pretty-printing, but nothing necessarily unsurmountable. Probably, as you suggest also, sub-classing would help more. -- Joel