From: Andy Wingo <wingo@pobox.com>
To: "Neil Jerram" <neiljerram@googlemail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Plan for 2.0
Date: Sun, 04 Jan 2009 17:27:30 +0100 [thread overview]
Message-ID: <m37i5brq8d.fsf@pobox.com> (raw)
In-Reply-To: <49dd78620901031038i6f6c678o5cebc21b217374d2@mail.gmail.com> (Neil Jerram's message of "Sat, 3 Jan 2009 18:38:13 +0000")
Hi Neil,
On Sat 03 Jan 2009 19:38, "Neil Jerram" <neiljerram@googlemail.com> writes:
> We're clearly moving towards a 2.0 release. Here is my attempt to
> pull that together a bit and flesh out what needs to be done.
I think the plan is sensible.
> 2. The "vm" branch. Once the review of "master" is done, we'll merge
> "vm" into "master".
I still need to finish documenting things, and tying up loose ends. I'm
especially concerned about ABI and future compatibility. But this can be
done in vm or master.
> I'm wondering now if we should instead move the GH code into a
> separate library, "libgh", but continue to provide this as part of the
> Guile distribution.
If we do this, the resulting "product" should have "deprecated"
somewhere in its name. You wouldn't want people mistaking it for
"high-level".
My personal opinion is that we should move this stuff to C files that
the user can include in her own project, and distribute those C files
somewhere. But perhaps this is not feasible.
> That's all for now. Any concerns or comments?
Yay! :-)
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-01-04 16:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 18:38 Plan for 2.0 Neil Jerram
2009-01-04 15:35 ` David Séverin
2009-01-04 16:25 ` Neil Jerram
2009-01-05 13:47 ` Neil Jerram
2009-01-05 15:21 ` David Séverin
2009-01-07 23:18 ` Neil Jerram
2009-01-04 16:27 ` Andy Wingo [this message]
2009-01-05 0:50 ` Greg Troxel
2009-01-05 17:21 ` Ludovic Courtès
2009-01-07 23:22 ` Neil Jerram
2009-01-08 13:48 ` Ludovic Courtès
2009-01-16 0:25 ` Neil Jerram
2009-01-17 23:05 ` BDW-GC-Guile incompatibilities Ludovic Courtès
2009-01-30 22:31 ` Neil Jerram
2009-02-18 22:50 ` Ludovic Courtès
2009-01-17 23:08 ` Plan for 2.0 Ludovic Courtès
2009-01-07 23:16 ` Neil Jerram
2009-01-08 21:43 ` Ludovic Courtès
2009-01-09 13:53 ` Neil Jerram
2009-01-12 17:08 ` Ludovic Courtès
2009-01-12 21:14 ` Neil Jerram
2009-01-12 22:12 ` Neil Jerram
2009-01-09 14:22 ` David Séverin
2009-01-12 11:10 ` 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=m37i5brq8d.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=neiljerram@googlemail.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).