From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: [PATCH] Static allocation of GOOPS' SMOB and port class arrays
Date: Sun, 18 Jan 2009 21:16:17 +0100 [thread overview]
Message-ID: <8763kc74ku.fsf@gnu.org> (raw)
Hello!
In the BDW-GC branch, I committed these two pairs of patches:
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=c891a40e9fc5f718bfaf6e70f8fd0b19311d14a6
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=474554694f5618be238054e736540f567a0e02a0
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=0953b549464e5bf1433e7f0b8a49ac4b464c3c11
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=63385df2fdc2f9bc70804383f071f2fb74743a86
The first of each pair defines constants for the maximum number of
SMOB/port types and uses them, which clarifies the code.
The second changes `goops.c' so that the `scm_{smob,port}_class' arrays
are statically allocated.
If nobody objects in the next few days, I'll commit them to `master'.
Thanks,
Ludo'.
next reply other threads:[~2009-01-18 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 20:16 Ludovic Courtès [this message]
2009-02-02 23:10 ` [PATCH] Static allocation of GOOPS' SMOB and port class arrays Ludovic Courtès
2009-02-03 23:11 ` Neil Jerram
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=8763kc74ku.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).