From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Wingo Newsgroups: gmane.lisp.guile.devel Subject: Re: problem with trailing comment in repl Date: Sun, 13 Feb 2011 20:19:54 +0100 Message-ID: References: <87r5beb7dg.fsf@gnu.org> <8739ntbd8a.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1297624532 21209 80.91.229.12 (13 Feb 2011 19:15:32 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 13 Feb 2011 19:15:32 +0000 (UTC) Cc: "Jose A. Ortega Ruiz" , guile-devel@gnu.org To: Noah Lavine Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sun Feb 13 20:15:27 2011 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 1PohPq-00071h-NW for guile-devel@m.gmane.org; Sun, 13 Feb 2011 20:15:27 +0100 Original-Received: from localhost ([127.0.0.1]:49536 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PohPf-0003nI-Dp for guile-devel@m.gmane.org; Sun, 13 Feb 2011 14:15:15 -0500 Original-Received: from [140.186.70.92] (port=53651 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PohPa-0003j2-9y for guile-devel@gnu.org; Sun, 13 Feb 2011 14:15:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PohPF-0005Wq-IP for guile-devel@gnu.org; Sun, 13 Feb 2011 14:14:50 -0500 Original-Received: from a-pb-sasl-sd.pobox.com ([64.74.157.62]:62506 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PohPF-0005Wh-BV; Sun, 13 Feb 2011 14:14:49 -0500 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTP id B5E9F4882; Sun, 13 Feb 2011 14:15:51 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=zi1CsrrYIImyBjBLWSJYazqSTVU=; b=AvyjrK tneREcy7T5fupotJDvmumAELVT8kJHDcu8xBOGT97HKIyB4RBQEX/JRi9KQ6HWwW P2TguITGetKO+ZPf8eKtIViqqnCzpnvk+p7eQ6oIolVFXaHEvK4dY3KdAUJXOmB6 2Wqln2WXa4j8tgSUAtA2Mt2f161j0ScklhsFo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=f+/HRIdK89BebCYnT92NVbOLVNrOSTm0 v3Z1GIEXIQGlZE89zWFsNaU/Pg8ld/ogIXsCYCj64Ak+2I901d1MKQa+G8A/HF03 lEb0Go4qD6Mf3DlHQw3lo5IFpmv21BaOlylM9HP2uFMygSlFLCM7weJT38BYfo+P htE/wkTNhHk= Original-Received: from a-pb-sasl-sd.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTP id 92ECD4881; Sun, 13 Feb 2011 14:15:49 -0500 (EST) Original-Received: from unquote.localdomain (unknown [90.164.198.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTPSA id A7925487D; Sun, 13 Feb 2011 14:15:46 -0500 (EST) In-Reply-To: (Noah Lavine's message of "Sun, 13 Feb 2011 10:22:24 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-Pobox-Relay-ID: AACA239E-37A5-11E0-BC52-AF401E47CF6F-02397024!a-pb-sasl-sd.pobox.com X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 64.74.157.62 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:11601 Archived-At: Hi Noah, I think it makes sense to have a reader that actually returns comments. That, to me, is the general solution: the REPL reader just treats a comment as whitespace. On Sun 13 Feb 2011 16:22, Noah Lavine writes: > - The quicker way: if the language in use is scheme, change the > next-char function (repl.scm line 205) to know about comments, so that > if it saw a semicolon, it would snarf everything until the end of the > line. Nasty, but a good idea I think! Care to submit a patch? :) Andy -- http://wingolog.org/