From: "David Séverin" <david@altosw.be>
To: "Neil Jerram" <neiljerram@googlemail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Plan for 2.0
Date: Sun, 4 Jan 2009 13:35:22 -0200 [thread overview]
Message-ID: <20090104133522.5ef7df67@altosw.be> (raw)
In-Reply-To: <49dd78620901031038i6f6c678o5cebc21b217374d2@mail.gmail.com>
Hi Guilers,
It might be a small thing [and of course not a priority at all], but I'd love to see
a small evolution of the manual index structure in order to separate scheme
procedures from others, scheme variables from others...:
* Concept Index
* Scheme Prodedure Index * C Procedure Index
* Scheme Variable Index * C Variable Index
* Scheme Type Index * C Type Index
* R5RS Index
Being a scheme 'only' programmer, I'd love not to have to scroll through
gh_* and scm_* ... when I am looking for something in an index.
David
;; --
Le Sat, 3 Jan 2009 18:38:13 +0000,
"Neil Jerram" <neiljerram@googlemail.com> a écrit :
> 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.
>
> What will go into 2.0:
>
> 1. The git "master" branch. In principle, everything here, but we
> need to review and check for
>
> - anything that should be excluded
>
> - any applicable fixes that were made in 1.8.x and didn't get copied
> to master.
>
> I've started doing this review and will hopefully complete soon. If
> there is anything that shouldn't be in 2.0, I'll move it into a new
> branch. If there are missing fixes from 1.8.x, I'll cherry pick them
> into master.
>
> 2. The "vm" branch. Once the review of "master" is done, we'll merge
> "vm" into "master".
>
> 3. The "ossau-gds-dev" branch. This contains some minor improvements
> to the Emacs interface. After the review of "master" is done, we'll
> merge "ossau-gds-dev" into "master".
>
> 4. Any other changes (including bug fixes) that we think are important
> to get done before 2.0. I propose to review the bugs in Savannah, and
> also recent email discussions, to identify these.
>
> Is there anything else? In particular, am I right in thinking that
> the BDW-GC work is not ready yet?
>
> One specific query... Although I advocated removing GH before, I
> don't feel 100% confident that that's the right thing for 2.0. 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. Moving the code out of libguile will still achieve the
> important objectives of (1) reducing the size of the libguile code
> that developers need to look at and work with, and (2) ensuring that
> GH is implementable on top of the advertised SCM API; but keeping
> libgh in the distribution will be a significant help for users who are
> still using GH (who will just need to add -lgh to their link line).
>
> I still think we should remove all GH-related documentation, as we
> don't want to do anything to encourage further GH usage. The GH code
> itself is sufficient IMO for showing how someone can migrate their
> code from GH to SCM.
>
> That's all for now. Any concerns or comments?
>
> Regards,
> Neil
>
>
next prev parent reply other threads:[~2009-01-04 15:35 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 [this message]
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
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=20090104133522.5ef7df67@altosw.be \
--to=david@altosw.be \
--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).