From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Rob Browning Newsgroups: gmane.lisp.guile.devel Subject: Re: Adding srfi-30 comments. Date: Tue, 03 Sep 2002 13:14:02 -0500 Sender: guile-devel-admin@gnu.org Message-ID: <87lm6j0wlx.fsf@raven.i.defaultvalue.org> References: <87admz3b3f.fsf@raven.i.defaultvalue.org> <87wuq3c94w.fsf@zagadka.ping.de> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1031076811 8356 127.0.0.1 (3 Sep 2002 18:13:31 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 3 Sep 2002 18:13:31 +0000 (UTC) Cc: guile-devel@gnu.org Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 17mIB7-0002Ae-00 for ; Tue, 03 Sep 2002 20:13:29 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17mICg-0003D4-00; Tue, 03 Sep 2002 14:15:06 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 17mIBk-00031T-00 for guile-devel@gnu.org; Tue, 03 Sep 2002 14:14:08 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 17mIBg-000318-00 for guile-devel@gnu.org; Tue, 03 Sep 2002 14:14:08 -0400 Original-Received: from dsl-209-87-109-2.constant.com ([209.87.109.2] helo=defaultvalue.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17mIBg-00030y-00 for guile-devel@gnu.org; Tue, 03 Sep 2002 14:14:04 -0400 Original-Received: from raven.i.defaultvalue.org (raven.i.defaultvalue.org [192.168.1.7]) by defaultvalue.org (Postfix) with ESMTP id D9F7EA1B2; Tue, 3 Sep 2002 13:14:02 -0500 (CDT) Original-Received: by raven.i.defaultvalue.org (Postfix, from userid 1000) id 9F79181D; Tue, 3 Sep 2002 13:14:02 -0500 (CDT) Original-To: Marius Vollmer In-Reply-To: <87wuq3c94w.fsf@zagadka.ping.de> (Marius Vollmer's message of "03 Sep 2002 18:47:59 +0200") Original-Lines: 39 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-pc-linux-gnu) Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:1261 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:1261 Marius Vollmer writes: > Would we be compliant if we just extend the existing code that handles > #! !# to handle #| |# as well? If so, I don't see why we shouldn't do > it right away. I'd have to do some testing to be sure. The primary requirements seem to be: - #| comments are visible to scheme as a single whitespace - an error is signaled if a closing is |# not found. - #| comments can be nested - R5RS is not extended so tokens, etc. must be separated from #| comments by a regular R5RS . I presume this means that you want foo #|bar|#, not foo#|bar|#. If our #! handling accmodates these requirements, then we're set, though we might want to specify how #! and #| interact. I'd be likely to propose: - a multi-line comment started with #! must end with !#. - a multi-line comment started with #| must end with |#. - #! and #| comments may be nested. and perhaps even - a #! multi-line comment is only permitted at the start of a scheme file. though perhaps there are good reasons not to specify that... -- Rob Browning rlb @defaultvalue.org, @linuxdevel.com, and @debian.org Previously @cs.utexas.edu GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel