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, 06 Nov 2007 21:54:59 +0000 [thread overview]
Message-ID: <87d4un6nv0.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87zlxzmnqp.fsf@laas.fr> (Ludovic Courtès's message of "Wed, 31 Oct 2007 14:12:46 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> Besides, I think using libgc would yield a number of practical
> improvements for the end user: `scm_set_smob_mark ()' would become
> useless in most cases
I think I understand the point here, and it seems to me that this is
an improvement for the developer, not for the end user; and IMO not a
significant one (because it's pretty trivial to write a smob mark
function). It also implies a performance cost, from scanning regions
of SMOB memory that Guile currently knows cannot contain heap
pointers.
> and so would `scm_dynwind_free ()',
> `scm_set_smob_free ()' could be avoided almost entirely in guile-core,
> memory leaks would become less likely in the presence of non-local
> exists, marking a tree-like structure would just work (see
> http://thread.gmane.org/gmane.lisp.guile.bugs/3558), etc.
(I don't understand these ones in detail, so there may well be
significant benefits here.)
> OK, so my goals for 1.9 would be:
>
> * Evaluate `libgc'-based Guile (see above).
>
> * Rewrite the interpreter in Scheme (or a subset thereof), with a
> tiny Scheme-to-C compiler. That could be done in such a way that we
> could re-use, e.g., the memoization and unmemoization code that
> already exists in the first step.
Interesting. Do you think that that would be a lot faster than the C
code we have now?
> * Provide a documented C doc snarfing tool, written in Scheme, with a
> public Scheme doc snarfing API. I started looking at it based on
> the modules I wrote for doc-snarfing in Guile-{Reader,Avahi,GnuTLS}.
Great; I've been thinking that we need this too.
> * Provide some Unicode support. The hardest part, I think, is that
> we'd probably need to rewrite/extend the C port API.
I'm pretty Unicode-ignorant, but I've read enough to think that this
area is important. Is the problem with the C API just that it has
"char" everywhere?
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-11-06 21:54 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 [this message]
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=87d4un6nv0.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).