unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: "Julian Graham" <joolean@gmail.com>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: [r6rs-discuss] Implementors' intentions concerning R6RS
Date: Tue, 30 Oct 2007 23:15:25 +0000	[thread overview]
Message-ID: <874pg8w5wy.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <2bc5f8210710300801o6de398aeg968bcb73bb0cc5e@mail.gmail.com> (Julian Graham's message of "Tue, 30 Oct 2007 11:01:05 -0400")

"Julian Graham" <joolean@gmail.com> writes:

> Well, for what it's worth, faster live "interpretation" of Scheme is
> really important to me, whether that means some kind of Scheme JIT
> compilation a la GNU Lightning or whatever.  I'm still fairly wed to
> being able to "script" my C code with Scheme dynamically, so I hope
> Guile's not moving away from that significantly.

I don't think anyone intends that.

>  Other non-specific,
> poorly-researched desires for 1.9:
>
> * Faster GC

From the recent experiments vs. Boehm GC, my impression was that
Guile's GC is already pretty good and that there is little scope for
improvement here.

> (this is probably pretty similar to "faster interpretation")

Actually that's a completely different matter.  There are lots of
options here; for example, Keisuke Nishida's VM work.

> * Integrated debugging and profiling tools

Absolutely.

> * Guile was initially proposed as a multi-language scripting platform;
> is that still part of the mission?

IMO, after umpteen years of not-happening, it would be silly for us to
say that this is still a core part of the mission.  But technically I
think this is still an interesting idea.  There's a load of half-done
stuff out there: Thomas Bushnell's Python, Ian Bicking's Tcl, Ctax, my
Elisp; a good first step would be just to pull that all together, and
see if there's a coherent big picture.  For Python there's also the
possibility of leveraging PyPy.

> * Not related to 1.9 itself, but maybe a cleanup / redesign of the web
> page,

Yes, in principle.  Needs someone to volunteer though.

> including a cleanup of active projects,

That's in my list too.

> better integration with Savannah for bug tracking, etc.

I started looking at this this week.  After a bit of thought, I'm
thinking that even if we automatically gatewayed bug-guile emails into
the Savannah tracker, we'd still want to review the new bugs as they
appear - and so we might as well just cut and paste them from
bug-guile by hand.

> * Thorough updating of the documentation

Agreed.  That's on my list, but one can't have too much help!

> * Integration with Free Software VMs -- Bigloo currently lets you
> compile Scheme to CIL; it would be neat if you could do the same with
> Guile and then run on top of DotGNU.  Or Kaffe.  Or anything else.

Yes, that would be nice.  Except I'm not keen on following Microsoft
"standards".  Java VM and/or Parrot (is that still happening?) would
be fine.

Regards,
        Neil



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


  reply	other threads:[~2007-10-30 23: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 [this message]
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=874pg8w5wy.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=joolean@gmail.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).