unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: release update
Date: Sat, 20 Jun 2009 13:00:42 +0200	[thread overview]
Message-ID: <m37hz7890l.fsf@pobox.com> (raw)
In-Reply-To: <86iqitw915.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 18 Jun 2009 23:01:58 +0200")

On Thu 18 Jun 2009 23:01, ludo@gnu.org (Ludovic Courtès) writes:

>> guile-config and pkg-config
>
> We should deprecate the former, BTW, if this hasn't already been done.

Indeed, though we need to keep it working through 2.0, at least until
new guile.m4 (yet to be ported...) becomes common.

>> (system xref), procedure-callers, procedure-callees, can work as
>> variables get redefined
>
> I think this should be added to the manual as well.

Yes.

>> BUG: SCM_SNAME -> SCM_SUBR_NAME
>
> Ooh, I didn't worry much about it back then.  Should we?

I fixed this one. SNAME was very confusing to me :)

>> FIXME: update copyrights
>
> Yes.
>
> (There's "(add-hook 'write-file-hooks 'copyright-update)", which I find
> convenient.)

Looks like Neil took care of things. I've added this one to my .emacs.

>> ecmascript support?
>
> Yes, although it's currently undocumented.

Indeed, needs fixing.

>> new function: scm_module_public_interface
>
> Speaking of which, I was thinking at some point about adding a
> `public-interface' slot to `module-type', to avoid hash table lookups.
> What do you think?

Yes! %module-public-interface is a terrible hack.

Andy
-- 
http://wingolog.org/




  reply	other threads:[~2009-06-20 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 22:05 release update Andy Wingo
2009-06-17 22:46 ` Neil Jerram
2009-06-18 21:01 ` Ludovic Courtès
2009-06-20 11:00   ` Andy Wingo [this message]
2009-06-20 13:34     ` 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=m37hz7890l.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).