From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55667 invoked by alias); 10 Jan 2019 16:44:32 -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 55643 invoked by uid 89); 10 Jan 2019 16:44:31 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=prompted, interest, management X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 Jan 2019 16:44:30 +0000 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7EB3A142BFE; Thu, 10 Jan 2019 16:44:29 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id B173E68894; Thu, 10 Jan 2019 16:44:27 +0000 (UTC) Subject: Re: [PATCH 00/12] Remove some ALL_* iteration macros To: Tom Tromey , gdb-patches@sourceware.org References: <20181125165439.13773-1-tom@tromey.com> From: Pedro Alves Message-ID: Date: Thu, 10 Jan 2019 16:44:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181125165439.13773-1-tom@tromey.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-01/txt/msg00215.txt.bz2 Hi Tom, On 11/25/2018 04:54 PM, Tom Tromey wrote: > This series removes various ALL_* iteration macros, in favor of C++ > iterators, range adapters, and ranged for loops. I've been wanting > this for a while, because it helps a little bit with various > experiments of mine that involve changing objfile lifetime management; > Pedro's thread iterator patch prompted me to finally do this. I'm only now catching up with this. Thanks so much for doing it! > There are still a few more such macros that could be converted. And, > I think inf_threads_iterator could be converted to use next_iterator. > I can do some of this if there's interest. If it's a natural fit, then I think it'd be nice. Is there a downside? Thanks, Pedro Alves