From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: vm merged to master
Date: Sat, 14 Mar 2009 15:36:12 +0100 [thread overview]
Message-ID: <87vdqcqihv.fsf@gnu.org> (raw)
In-Reply-To: m37i2tuis6.fsf@pobox.com
Hello!
Andy Wingo <wingo@pobox.com> writes:
> I went ahead and merged VM to master.
Great!
> Things went fine after a couple of
> manual merges, though `(procedure-property apply 'arity)' needs some
> work -- see the log for 5442b3a5989a118f2addf3190eab2e27d65e0658.
Right, that won't work if `apply' is a program. The question is: what
should we do with procedure properties? Before the VM, they could be
used both with subrs and Scheme closures. I think it would be nice if
we could extend them so that they worked transparently with programs as
well, maybe by attaching per-program procedure properties lazily. What
do you think?
> I should be happy but really I'm just tired ;) Can people please check
> this out, give it some pounding and report any errors to the list.
>
> Errors running external code modules are especially appreciated --
> existing code should still work, with very few exceptions.
The only troubles I had so far are:
- the `object-ref' limitation to 256 objects;
- `current-reader' not taken into account;
- circular references among modules (previously worked around via
autoloads) not supported---but this is a good thing, it's an
opportunity to remove kludges. :-)
I'll eventually proceed with the merge in the BDW-GC branches.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-03-14 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 23:04 vm merged to master Andy Wingo
2009-03-14 13:19 ` Neil Jerram
2009-03-16 22:48 ` Andy Wingo
2009-03-19 0:51 ` Neil Jerram
2009-03-14 14:36 ` Ludovic Courtès [this message]
2009-03-16 22:54 ` Andy Wingo
2009-03-15 0:01 ` Greg Troxel
2009-03-16 21:53 ` Andy Wingo
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=87vdqcqihv.fsf@gnu.org \
--to=ludo@gnu.org \
--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).