From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Neil Jerram Newsgroups: gmane.lisp.guile.devel Subject: Re: [PATCH] Per-module reader, take #2 Date: Thu, 20 Oct 2005 22:27:15 +0100 Message-ID: <871x2fangs.fsf@ossau.uklinux.net> References: <87u0gp9lm3.fsf@laas.fr> <877jd3lkdq.fsf@ossau.uklinux.net> <87hdc62a6c.fsf@laas.fr> <87irw49twc.fsf@laas.fr> <87irw3prgp.fsf@ossau.uklinux.net> <8764rw7b9q.fsf_-_@laas.fr> <871x2j98qb.fsf@ossau.uklinux.net> <87u0ffnudk.fsf@laas.fr> <87sluxb0xt.fsf@ossau.uklinux.net> <87sluxugm1.fsf@zip.com.au> <87d5m0ty8f.fsf@laas.fr> <87wtk89ean.fsf@zip.com.au> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1129843724 30378 80.91.229.2 (20 Oct 2005 21:28:44 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 20 Oct 2005 21:28:44 +0000 (UTC) Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Thu Oct 20 23:28:42 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EShx4-0005Tw-EM for guile-devel@m.gmane.org; Thu, 20 Oct 2005 23:27:54 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EShx3-0001qz-KW for guile-devel@m.gmane.org; Thu, 20 Oct 2005 17:27:53 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EShwa-0001Pg-CD for guile-devel@gnu.org; Thu, 20 Oct 2005 17:27:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EShwY-0001Md-2R for guile-devel@gnu.org; Thu, 20 Oct 2005 17:27:23 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EShwX-0001MO-TF for guile-devel@gnu.org; Thu, 20 Oct 2005 17:27:21 -0400 Original-Received: from [80.84.72.33] (helo=mail3.uklinux.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EShwX-0006cR-QL for guile-devel@gnu.org; Thu, 20 Oct 2005 17:27:22 -0400 Original-Received: from laruns (host81-130-181-102.in-addr.btopenworld.com [81.130.181.102]) by mail3.uklinux.net (Postfix) with ESMTP id B0513409FB4 for ; Thu, 20 Oct 2005 21:27:20 +0000 (UTC) Original-Received: from laruns (laruns [127.0.0.1]) by laruns (Postfix) with ESMTP id 26B806F6CE for ; Thu, 20 Oct 2005 22:27:15 +0100 (BST) Original-To: guile-devel@gnu.org In-Reply-To: <87wtk89ean.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 21 Oct 2005 05:30:40 +1000") User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) 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:5335 Archived-At: Kevin Ryde writes: > ludovic.courtes@laas.fr (Ludovic Court=E8s) writes: >> >> And what exactly would happen to >> `primitive-load' (which is the one that triggered the call to >> `my-zany-reader') when `my-zany-reader' returns? > > It sees eof, and stops. Or it sees the rest of the file if the new > reader only takes an inlined middle bit of special syntax. A nested > parser like that seems pretty clean and pretty normal to me. I think > it can do almost everything you're aiming for. I think Kevin is right that this is possible and would work, but there is also some merit in the arguments that - even if it is possible, emulating/duplicating the primitive-load loop is a bit dull - in future the primitive-load loop might acquire more features, and it would be nice if those features Just Worked for Ludovic's readers also. On the second point there's a specific feature that I have in mind, namely being able to set previously specified breakpoints on each expression as soon as it has been read, and before it is evaluated, so I'm not just speculating wildly. So I think the fluid current reader approach is quite nice, as long as we are happy that it doesn't introduce any significant performance overhead. Regards, Neil _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel