unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Klaus Schilling <schilling.klaus@web.de>
To: neil@ossau.uklinux.net
Cc: elf@ephemeral.net, guile-devel@gnu.org
Subject: Re: [r6rs-discuss] Implementors' intentions concerning R6RS
Date: Sat, 03 Nov 2007 19:15:39 +0100 (CET)	[thread overview]
Message-ID: <20071103.191539.92583289.schilling.klaus@web.de> (raw)
In-Reply-To: <87640rm7ec.fsf@ossau.uklinux.net>

From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: [r6rs-discuss] Implementors' intentions concerning R6RS
Date: Sun, 28 Oct 2007 18:16:43 +0000

> Elf <elf@ephemeral.net> writes:
> 
> > (i usually start people off with guile nowadays,
> > despite its non-r5 compliance, as the wizard book is still around r4 material.)
> 
> I hope you don't mind me emailing you in response to your r6rs post;
> I'm one of the Guile developers.
> 
> I wondered if you could say more about the r5-non-compliance that you
> perceive?  I thought we had solved all r5 compliance issues by now.

no, as Guile's symbols are still case-sensitive which is illegal in r5rs

Klaus Schilling


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


  parent reply	other threads:[~2007-11-03 18:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <818B5317-4F09-46F3-9376-43292CEB3C16@iro.umontreal.ca>
     [not found] ` <200710261850.l9QIo8Vu017241@garbo.cs.indiana.edu>
     [not found]   ` <Pine.LNX.4.61.0710261701241.9685@tesseract.thetesseract.org>
     [not found]     ` <47229C5E.8070406@emf.net>
     [not found]       ` <Pine.LNX.4.61.0710280508300.19352@tesseract.thetesseract.org>
2007-10-28 18:16         ` [r6rs-discuss] Implementors' intentions concerning R6RS Neil Jerram
2007-10-28 18:29           ` Elf
     [not found]           ` <Pine.LNX.4.61.0710281146460.32075@tesseract.thetesseract.org>
2007-10-28 19:28             ` Neil Jerram
2007-10-29 15:30               ` Ludovic Courtès
2007-10-29 21:51                 ` Neil Jerram
2007-10-30  9:50                   ` Ludovic Courtès
2007-10-30 15:01                     ` Julian Graham
2007-10-30 23:15                       ` Neil Jerram
2007-10-31 14:55                         ` Julian Graham
2007-10-31 13:12                       ` Ludovic Courtès
2007-11-06 21:54                         ` Neil Jerram
2007-11-11 15:28                           ` Ludovic Courtès
2007-11-12 20:29                             ` Neil Jerram
2007-11-12 20:51                               ` Ludovic Courtès
2007-10-30 22:53                     ` Neil Jerram
2007-10-31 10:30                       ` Ludovic Courtès
2007-11-02 20:53                       ` Klaus Schilling
2007-11-03 11:14                         ` Ludovic Courtès
2007-11-03 17:49                           ` Klaus Schilling
2007-10-30 23:55               ` Andy Wingo
2007-11-03 18:15           ` Klaus Schilling [this message]
2007-11-04 12:39             ` Ludovic Courtès

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=20071103.191539.92583289.schilling.klaus@web.de \
    --to=schilling.klaus@web.de \
    --cc=elf@ephemeral.net \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).