From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30497 invoked by alias); 24 Jul 2011 13:48:27 -0000 Received: (qmail 30488 invoked by uid 22791); 24 Jul 2011 13:48:27 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-gy0-f169.google.com (HELO mail-gy0-f169.google.com) (209.85.160.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 24 Jul 2011 13:48:09 +0000 Received: by gyg13 with SMTP id 13so2124620gyg.0 for ; Sun, 24 Jul 2011 06:48:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.200.131 with SMTP id z3mr4465936yhn.322.1311515288505; Sun, 24 Jul 2011 06:48:08 -0700 (PDT) Received: by 10.236.109.131 with HTTP; Sun, 24 Jul 2011 06:48:07 -0700 (PDT) In-Reply-To: <20110724125222.GA8403@host1.jankratochvil.net> References: <20110715191920.GA29975@host1.jankratochvil.net> <20110724125222.GA8403@host1.jankratochvil.net> Date: Sun, 24 Jul 2011 15:59:00 -0000 Message-ID: Subject: Re: [rfc] Be in language c more c++ compatible From: Matt Rice To: Jan Kratochvil Cc: gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes 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 X-SW-Source: 2011-07/txt/msg00665.txt.bz2 On Sun, Jul 24, 2011 at 5:52 AM, Jan Kratochvil wrote: > On Sat, 23 Jul 2011 23:17:43 +0200, Matt Rice wrote: >> was curious what it did with the attached objc++ version. >> >> which isn't really a supported language by any means. > > I think this is outside of the scope of this thread. > Yeah, I pretty much came to the same conclusion, after stewing on it overnight except as it relates to: >>There was another mail about use case when you >>combine C/C++ application/libs. since objc++ is typically used to bridge a c++ library with an objective-c library, and not generally a language used to write in directly. there is also more opportunity for 'set language', in both languages with the current language being objective-c and setting to c++, but also the current language being c++ and wanting to be objective-c. what made me think of it, is the last time I was debugging a mixed c++/objective-c program, having to call 'set language', was extremely annoying, to the point that I added commands to my .gdbinit to lighten the churn. define cp set language c++ end define oc set language objective-c end and setting the language was mostly something done in response to some failed command. Thus, I personally think anything that lessens the amount of 'set language'ing is a good idea.