From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10606 invoked by alias); 16 Sep 2010 19:09:48 -0000 Received: (qmail 10597 invoked by uid 22791); 16 Sep 2010 19:09:48 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Sep 2010 19:09:43 +0000 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o8GJ9e3L010495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Sep 2010 15:09:40 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o8GJ9dna021624; Thu, 16 Sep 2010 15:09:39 -0400 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id o8GJ9cON013284; Thu, 16 Sep 2010 15:09:38 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id C67653784BE; Thu, 16 Sep 2010 13:09:37 -0600 (MDT) From: Tom Tromey To: Joel =?utf-8?Q?Borggr=C3=A9n-Franck?= Cc: gdb@sourceware.org Subject: Re: Python API questions and use cases References: Date: Thu, 16 Sep 2010 19:09:00 -0000 In-Reply-To: ("Joel =?utf-8?Q?Borggr=C3=A9n-Franck=22's?= message of "Thu, 16 Sep 2010 09:32:31 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 X-SW-Source: 2010-09/txt/msg00100.txt.bz2 >>>>> "Joel" =3D=3D Joel Borggr=C3=A9n-Franck writes: Joel> Ok. I've approached the Python API as a (eventually) complete replace= ment Joel> for GDB-script, so whenever I have to use parse_and_eval I feel it's = an Joel> (ugly) hack. This is perhaps not the intention? We want it to be complete, but there will probably always be some uses where parse_and_eval is the most convenient thing to do. We're definitely interested in hearing about holes in the API. It is fine to just file bug reports as you run across them. Tom