unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Elf <elf@ephemeral.net>, Guile Development <guile-devel@gnu.org>
Subject: Re: [r6rs-discuss] Implementors' intentions concerning R6RS
Date: Tue, 30 Oct 2007 10:50:18 +0100	[thread overview]
Message-ID: <877il57wyt.fsf@laas.fr> (raw)
In-Reply-To: <87ejfd7fnq.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon\, 29 Oct 2007 21\:51\:53 +0000")

Hi Neil,

Neil Jerram <neil@ossau.uklinux.net> writes:

> ludovic.courtes@laas.fr (Ludovic Courtès) writes:

>>  With that goal in mind, the pure
>> interpreter approach is not sustainable
>
> ... but I don't see what you mean by this.

He, that was sort of a teaser.  ;-)

When I started using Guile, I was fully in sync with the "embeddable
library" approach, which means that I'd write, say, 75% of an
application in C, and then arrange to have the remainder written in
Scheme in an extensible fashion.

But I started really enjoying Scheme and wanting to write less C, more
Scheme.  So why bother writing C at all when I could avoid it?  Well,
for "performance reasons".  And what are those "performance reasons"?
The interpreter is pretty slow, which is definitely not due to inherent
limitations of the language, but to the implementation.

I'm convinced that it's possible to write a Scheme interpreter much
faster than ours.  So I think that's one route we should take in 1.9.
The next step would be to have a compiler (to byte code, to C,
whatever).  However, I think the interpreter should keep playing a
central role in Guile (because it always did, and because it's often
convenient to work with an interpreter), which is why I would consider
improving/rewriting the interpreter a major goal for 1.9.

Maybe we should start a discussion about what we'd like to see in 1.9?
:-)

Thanks,
Ludovic.


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


  reply	other threads:[~2007-10-30  9:50 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 [this message]
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=877il57wyt.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --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).