unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: Block comments and `read-hash-extend'
Date: Mon, 04 Jul 2005 23:26:11 +0100	[thread overview]
Message-ID: <42C9B783.7080204@ossau.uklinux.net> (raw)
In-Reply-To: <87fyvh4exx.fsf@laas.fr>

Ludovic Courtès wrote:
> Hi,
> 
> Kevin Ryde <user42@zip.com.au> writes:
> 
> 
>>The manual says the !# is supposed to appear on a line on its own.  Do
>>you think you need it joined on?
> 
> 
> I think I should have read the manual more carefully.  ;-)  Indeed, `!#'
> needs to be on a line on its own, so the bug I described above is not an
> actual bug, it's a feature.
> 
> Still, I don't understand the rationale behind this and I consider this
> a limitation.  In fact, it's misleading compared to block comments in
> other languages or in SRFI-30.

I agree with you.  I think the rationale for the status quo is actually
just historical accident, reflecting that the support for #! ... !# was
initially designed only for the `#! /usr/local/bin/guile' line at the
beginning of a script file.  But it surely much more useful for #! ...
!# comments to work as you suggest, and I can't see any downside from
making them do so.

	Neil


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2005-07-04 22:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16  9:37 Block comments and `read-hash-extend' Ludovic Courtès
2005-06-17  0:13 ` Kevin Ryde
2005-06-17  7:31   ` Ludovic Courtès
2005-06-17 22:40     ` Rob Browning
2005-09-04 22:59       ` Marius Vollmer
2005-09-04 23:57         ` Rob Browning
2005-07-04 22:26     ` Neil Jerram [this message]
2005-08-19  8:11 ` Ludovic Courtès
2005-09-04 23:02 ` Marius Vollmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42C9B783.7080204@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).