From owner-freebsd-bugs Thu Jul 27 1:50: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A497C37B92C for ; Thu, 27 Jul 2000 01:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA66540; Thu, 27 Jul 2000 01:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 27 Jul 2000 01:50:02 -0700 (PDT) Message-Id: <200007270850.BAA66540@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bertho Stultiens Subject: Re: misc/20172: byacc 1.9 fails to generate $default transitions for non-terminals Reply-To: Bertho Stultiens Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/20172; it has been noted by GNATS. From: Bertho Stultiens To: freebsd-gnats-submit@FreeBSD.org, bertho@j.auh.dk Cc: Subject: Re: misc/20172: byacc 1.9 fails to generate $default transitions for non-terminals Date: Thu, 27 Jul 2000 10:48:31 +0200 Two comments: 1) The example should use a slightly different action for one rule to make it more clear what happens. The yyclearin should eliminate the lookahead and then all should continue as planned. However, byacc will generate a syntax error on the input. Here is the rule as intended: line: tTOK xpr ',' xpr { if(yychar == tNL) { printf("Success: Got tNL\n"); yyclearin; } } 2) After some email exchange with the original author it has become apparent that he does not seem to consider the problem a bug. This means that it is likely that byacc will be unusable for all heavy yacc-parsers that manipulate lookahead tokens in an above fassion. Greetings Bertho To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message