From: Neil Jerram <neil@ossau.uklinux.net>
To: Guile Development <guile-devel@gnu.org>
Cc: Elf <elf@ephemeral.net>
Subject: Re: [r6rs-discuss] Implementors' intentions concerning R6RS
Date: Mon, 29 Oct 2007 21:51:53 +0000 [thread overview]
Message-ID: <87ejfd7fnq.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87d4uykkes.fsf@laas.fr> (Ludovic Courtès's message of "Mon, 29 Oct 2007 16:30:51 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> FWIW, my feeling about R6 as a whole is that it is not aligned with
>> Guile's objective - remembering that the latter is not just to be a
>> Scheme implementation, but a Scheme implementation in the form of an
>> embeddable library that is useful for extending applications. But my
>> thoughts on this haven't fully crystallised yet.
>
> Speaking of this, I hope you (Guile developers) don't mind my answer to
> Marc Feeley wrt. R6RS, which he posted on `r6rs-discuss' [0]. We
> haven't had a debate about it here, but I'd be glad if we had one.
Well I didn't mind. I was happy to see that Marc had received a
statement from "Guile", and I'm happy with what you said.
> BTW, as time passes, I am more and more doubtful about the "embeddable
> library" argument. After all, if we work on a Scheme implementation,
> that's certainly because we want to write Scheme. Sure we want to make
> it easy to interface with existing code written in C, but we also want
> to write *more* Scheme code.
^ Agreed up to here...
> With that goal in mind, the pure
> interpreter approach is not sustainable
... but I don't see what you mean by this.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-10-29 21:51 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 [this message]
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
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=87ejfd7fnq.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=elf@ephemeral.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).