From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30459 invoked by alias); 9 Oct 2006 12:33:55 -0000 Received: (qmail 30451 invoked by uid 22791); 9 Oct 2006 12:33:55 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 09 Oct 2006 12:33:47 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GWuKG-0002sg-LB; Mon, 09 Oct 2006 08:33:44 -0400 Date: Mon, 09 Oct 2006 12:33:00 -0000 From: Daniel Jacobowitz To: Rob Quill Cc: gdb@sourceware.org Subject: Re: YACC/Lex Message-ID: <20061009123343.GA11055@nevyn.them.org> Mail-Followup-To: Rob Quill , gdb@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00040.txt.bz2 On Mon, Oct 09, 2006 at 12:44:56PM +0100, Rob Quill wrote: > Hi, > > Is it ok to use code generated by YACC and/or Lex in GDB? If not, what > alternatives are there? Take a look at the several existing yacc parsers in GDB; there's also at least one lex parser. -- Daniel Jacobowitz CodeSourcery