From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8918 invoked by alias); 10 Feb 2009 01:30:55 -0000 Received: (qmail 8910 invoked by uid 22791); 10 Feb 2009 01:30:54 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 10 Feb 2009 01:30:48 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n1A1UgbI019752; Mon, 9 Feb 2009 20:30:42 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n1A1Udr2012616; Mon, 9 Feb 2009 20:30:40 -0500 Received: from opsy.redhat.com (vpn-12-231.rdu.redhat.com [10.11.12.231]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n1A1UdY9032134; Mon, 9 Feb 2009 20:30:39 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 5AAF88880F4; Mon, 9 Feb 2009 18:30:37 -0700 (MST) To: Doug Evans Cc: Eli Zaretskii , gdb-patches@sourceware.org Subject: Re: RFC: add ability to "source" Python code References: From: Tom Tromey Reply-To: Tom Tromey Date: Tue, 10 Feb 2009 01:30:00 -0000 In-Reply-To: (Doug Evans's message of "Sun\, 8 Feb 2009 17\:52\:46 -0800") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2009-02/txt/msg00214.txt.bz2 >>>>> "Doug" == Doug Evans writes: Doug> In the case of "source foo.py" I sort of disagree (that's the Doug> other 1/4, fwiw). Technically speaking it's possible that some Doug> bloke out there has a foo.py script that actually is gdb Doug> commands, and forcing the script to be interpreted as python Doug> would break that. It's seems really unlikely though. I think it is beyond unlikely, and more in the realm of "has never been done, ever, by any gdb user". Doug> Perhaps "source" could/should also take a -g option to force the Doug> script to be interpreted as gdb commands. It would be fine by me. Also I could add "--" to stop argument interpretation. I don't think anybody will ever actually use this, but it would make it obvious how to source a file with an odd name. Well... most odd names. You cannot source a file whose name ends in a space. Tom