From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Noah Lavine Newsgroups: gmane.lisp.guile.devel Subject: [PATCH] LALR Parser Documentation Fix Date: Tue, 26 Oct 2010 21:46:23 -0400 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: dough.gmane.org 1288144196 23427 80.91.229.12 (27 Oct 2010 01:49:56 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 27 Oct 2010 01:49:56 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Oct 27 03:49:55 2010 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PAv9H-0006nj-CB for guile-devel@m.gmane.org; Wed, 27 Oct 2010 03:49:55 +0200 Original-Received: from localhost ([127.0.0.1]:58792 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PAv6n-0001y5-Jn for guile-devel@m.gmane.org; Tue, 26 Oct 2010 21:47:21 -0400 Original-Received: from [140.186.70.92] (port=40349 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PAv6b-0001sJ-QX for guile-devel@gnu.org; Tue, 26 Oct 2010 21:47:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PAv5t-0003PG-J2 for guile-devel@gnu.org; Tue, 26 Oct 2010 21:46:26 -0400 Original-Received: from mail-wy0-f169.google.com ([74.125.82.169]:34861) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PAv5t-0003PA-Es for guile-devel@gnu.org; Tue, 26 Oct 2010 21:46:25 -0400 Original-Received: by wyf23 with SMTP id 23so226346wyf.0 for ; Tue, 26 Oct 2010 18:46:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Bm9HALODFqfb3Pts3mpxsrRv4LgnY0n/rODEgRFMFwE=; b=MayS/zqqOTfOhg3lUSB6zo8gRvTyp/fXmJ7REBymoJKTsk+GRu7H0UzfsY61sj41hb H+dr+k8MfvKe900Ss601ABABxNquoszWbKgtDr62Vdg/9kqrSuWvdqcth6KdRRYyOGEj SnXUUiCcXu7thoMNHVkl5DLSaIH8K7go81QSc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=CkgzB5i9iaQyx4KS4M1UhfM7ZM18Np+bKLGddHkA94sviNojNV6Q20ApEpJweKBElQ UMwqumukHe2R5zY6wHVyvb46HVgx3c+dc6XHPEWSmlXnJJrdlfT0PmqE0Y9n8d5iXU0U xC1BwibnpVnlvcy21iBiUWclEiXW5vnn0GhF8= Original-Received: by 10.216.55.208 with SMTP id k58mr8312477wec.90.1288143983065; Tue, 26 Oct 2010 18:46:23 -0700 (PDT) Original-Received: by 10.216.237.34 with HTTP; Tue, 26 Oct 2010 18:46:23 -0700 (PDT) X-Google-Sender-Auth: KZP-rHWksG4HGLdWK-2LntcqnVI X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:11072 Archived-At: The documentation for the LALR parser currently says that the tokenizer procedure passed to the parser should be a unary procedure taking a port, but the documentation at http://code.google.com/p/lalr-scm/wiki/ParserDefinition says it should be a thunk. The following patch fixes this: Noah diff --git a/doc/ref/api-lalr.texi b/doc/ref/api-lalr.texi index e19614c..95b0a85 100644 --- a/doc/ref/api-lalr.texi +++ b/doc/ref/api-lalr.texi @@ -25,12 +25,12 @@ Each rule has the form @code{(@var{non-terminal} (@var{rhs} right-hand sides, i.e., the production rule, and @var{action} is a semantic action associated with the rule. -The generated parser is a two-argument procedure that takes a @dfn{tokenizer} -and a @dfn{syntax error procedure}. The tokenizer should be a unary procedure -taking a port and returning a lexical token as produced by -@code{make-lexical-token}. The syntax error procedure may be called with at -least an error message (a string), and optionally the lexical token that caused -the error. +The generated parser is a two-argument procedure that takes a +@dfn{tokenizer} and a @dfn{syntax error procedure}. The tokenizer +should be a thunk that returns lexical tokens as produced by +@code{make-lexical-token}. The syntax error procedure may be called +with at least an error message (a string), and optionally the lexical +token that caused the error. @end deffn Please refer to the @code{lalr-scm} documentation for details.