From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84812 invoked by alias); 4 Aug 2017 11:28:41 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 83806 invoked by uid 89); 4 Aug 2017 11:28:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*r:sk:static., road X-HELO: mail-it0-f41.google.com Received: from mail-it0-f41.google.com (HELO mail-it0-f41.google.com) (209.85.214.41) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 04 Aug 2017 11:28:39 +0000 Received: by mail-it0-f41.google.com with SMTP id v127so6984575itd.0 for ; Fri, 04 Aug 2017 04:28:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=Im6jAGt8wlSpIByvMFFEMQulUtciW7GtuZMqrL8egp4=; b=omWHIbD/IY7aZSx16uYybkv/k83sthqaIyz+KqFih397hlKCC6NS4fFOUCNQ8f8Sm2 Ii5AtLpyuEwIPw6yFJlAP+R4QdBIeQkDCl7WJ2eLnouqiSPvCSUlcj1QE7rh7QgvRl9q yF4DnM0GogAcSEheQ7+WU5i3sUErungEE7ASFguie303DL1g8RDyn7U7SCEQVIkbz2G+ qBSgk7dbUtDSzW18+fkUJmKcxB6KRH6yv+YgdEVkSRXQgdav1oh8RsYQ8Jzxw2q+Ikmo R8ixyZqVmSB7SBjZAoxNWbujCMaKoP3fwS+TZjjEu5ie732aaeueMZA0AHwf8gk5q8XS FMgA== X-Gm-Message-State: AHYfb5gFoniaHucK//GHUEgseVrcgP5555MLjX6hz/9p6xNa+nbHtek7 M0QQmSAqdpQ4Pbwz X-Received: by 10.36.185.72 with SMTP id k8mr1879816iti.164.1501846117934; Fri, 04 Aug 2017 04:28:37 -0700 (PDT) Received: from E107787-LIN (static.42.136.251.148.clients.your-server.de. [148.251.136.42]) by smtp.gmail.com with ESMTPSA id i24sm634098iod.1.2017.08.04.04.28.36 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 04 Aug 2017 04:28:37 -0700 (PDT) From: Yao Qi To: Phi Debian Cc: "gdb\@sourceware.org" Subject: Re: Will GDB be rewritten in C++ (again) References: Date: Fri, 04 Aug 2017 11:28:00 -0000 In-Reply-To: (Phi Debian's message of "Wed, 2 Aug 2017 16:42:05 +0200") Message-ID: <86d18b3732.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-08/txt/msg00007.txt.bz2 Phi Debian writes: > Now I retrieved some bandwith and consider going back on GDB dev, but > still today I am reluctant with C++ > > So my question is, does this rewrite of GDB in C++ has been shelved or > is is still going? Phi, We don't _rewrite_ GDB in C++. As Joel said, GDB requires a C++11 compiler, because we started to use some C++-11 features. Most of the code is still written in C, and the code base isn't changed dramatically. > > For what I see on my distro, the gdb-7.11.1 is still C, so i would > guess that no progress has been done since 2012 ? > > PS: Don't flame on C++ vs C, my question is really about the road map > of GDB. If this is pure C I could refresh my mem to contribute, if > going C++ this is fine too, I would simply find other project there > are plenty :) One of the reasons that we move GDB to C++ is to make maintenance and development easier, not harder. You should feel easier to write code in GDB nowadays. --=20 Yao (=E9=BD=90=E5=B0=A7)