unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Luigi Semenzato" <luigi@semenzato.com>
To: "dsmich@adelphia.net" <dsmich@adelphia.net>
Cc: Andy Wingo <wingo@pobox.com>, bug-guile <bug-guile@gnu.org>,
	guile-user@gnu.org
Subject: Re: bug in read?
Date: Tue, 25 Sep 2007 09:22:19 -0700	[thread overview]
Message-ID: <c6bf18db0709250922u65536de0n434722c720245186@mail.gmail.com> (raw)
In-Reply-To: <30330998.1190568557000.JavaMail.root@web33>

Thank you for the explanation.

Does anybody know then why the Guile manual replicates
sections of r5rs instead of just pointing to them?
It's redundant and it leads to this kind of problems.

If Guile is Scheme version blah with some additions and
some omissions, shouldn't the manual just document
the additions and the omissions?

I don't mean to whine or lecture.  I am just wondering.

Thanks!
Luigi


On 9/23/07, dsmich@adelphia.net <dsmich@adelphia.net> wrote:
>
> ---- Andy Wingo <wingo@pobox.com> wrote:
> > Hi,
> >
> > Since it's a week later now and no one's answered:
> >
> > On Mon 17 Sep 2007 23:49, "Luigi Semenzato" <luigi@semenzato.com> writes:
> >
> > > Is this a reader bug?  Hash marks following
> > > an integer are interpreted as zeros, and the
> > > number is converted to real.
> > >
> > > guile> (read)
> > > 44###
> > > 44000.0
> > > guile>
> > >
> > > If this is expected, section 5.5.2.6 (Read Syntax for Numerical Data)
> > > should mention it.
>
> This is the syntax for inexact numbers.  See r5rs sections 6.2.4 and 7.1.1
>
> -Dale
>
>


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


  reply	other threads:[~2007-09-25 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-23 17:29 bug in read? dsmich
2007-09-25 16:22 ` Luigi Semenzato [this message]
2007-10-30 23:52   ` Neil Jerram
  -- strict thread matches above, loose matches on Subject: below --
2007-09-17 21:49 Luigi Semenzato
2007-09-23 15:54 ` Andy Wingo

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=c6bf18db0709250922u65536de0n434722c720245186@mail.gmail.com \
    --to=luigi@semenzato.com \
    --cc=bug-guile@gnu.org \
    --cc=dsmich@adelphia.net \
    --cc=guile-user@gnu.org \
    --cc=wingo@pobox.com \
    /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).