unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Subject: another #! !# problem
Date: Wed, 11 Aug 2004 05:54:34 -0700	[thread overview]
Message-ID: <411A170A.6050606@ccrma> (raw)

(begin
   (display 1)
#!
(display 2)
!#
)

gets:

ERROR: In procedure scm_lreadr:
ERROR: tmp34.scm:6:2: unexpected ")"
ABORT: (read-error)

whereas

(begin
#!
(display 2)
!#
   (display 1)
)

is ok.  This is the case in both the current CVS guile and version 1.6.4.



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


             reply	other threads:[~2004-08-11 12:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 12:54 Bill Schottstaedt [this message]
2004-08-11 21:54 ` another #! !# problem Kevin Ryde
2004-09-07  9:10   ` Marius Vollmer
2004-09-08  2:56     ` Rob Browning
2004-09-20 23:55       ` 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=411A170A.6050606@ccrma \
    --to=bil@ccrma.stanford.edu \
    /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).