Re: Plan for 2.0

2009-01-15 Thread Neil Jerram
2009/1/5 Ludovic Courtès l...@gnu.org: Hello! Neil Jerram neiljer...@googlemail.com writes: 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. I'd do (3) before (2) because

Re: Plan for 2.0

2009-01-12 Thread Ludovic Courtès
Hi, David Séverin lpce@gmail.com writes: Don't you think that the 'using thread' on debian [and other distro?] shouldn't be solved before to call a release '2.xx'? That Debian builds Guile --without-threads is a Debian-specific problem. The fact that Guile with and without threads

Re: Plan for 2.0

2009-01-12 Thread Neil Jerram
2009/1/12 Ludovic Courtès l...@gnu.org: Hello, Neil Jerram neiljer...@googlemail.com writes: That's good, but I think I didn't explain the possible problem fully, i.e. that the substitute won't work. Because of how Guile saves and restores continuations (by copying the stack), and how it

Re: Plan for 2.0

2009-01-12 Thread Neil Jerram
2009/1/12 Neil Jerram neiljer...@googlemail.com: 2009/1/12 Ludovic Courtès l...@gnu.org: Hello, Neil Jerram neiljer...@googlemail.com writes: That's good, but I think I didn't explain the possible problem fully, i.e. that the substitute won't work. Because of how Guile saves and restores

Re: Plan for 2.0

2009-01-09 Thread Neil Jerram
Hi Ludo! Thanks for your responses... 2009/1/8 Ludovic Courtès l...@gnu.org: Hi Neil, Neil Jerram neiljer...@googlemail.com writes: Use of Gnulib - linker warning - alloca - Have we inadvertently removed requirement for a real alloca? No. Gnulib's `alloca' provides a substitute when

Re: Plan for 2.0

2009-01-09 Thread David Séverin
Le Sat, 3 Jan 2009 18:38:13 +, Neil Jerram neiljer...@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: Hi Guilers, Don't you think that the 'using thread' on

Re: Plan for 2.0

2009-01-08 Thread Ludovic Courtès
Hi Neil, Neil Jerram neiljer...@googlemail.com writes: Below is a raw summary of all diffs between current branch_release-1-8 and master. Next step is to check that everything here is correct, and properly+fully documented in the manual and in NEWS. The Queries at the end are bits that I'm

Re: Plan for 2.0

2009-01-07 Thread Neil Jerram
2009/1/3 Neil Jerram neiljer...@googlemail.com: I've started doing this review and will hopefully complete soon. Below is a raw summary of all diffs between current branch_release-1-8 and master. Next step is to check that everything here is correct, and properly+fully documented in the manual

Re: Plan for 2.0

2009-01-07 Thread Neil Jerram
2009/1/5 David Séverin da...@altosw.be: Never used Texinfo :( I could learn, but right now I can not offer more than using guile and giving the best feedback I can on matters I feel knowledgeable enough to do so [I am alone managing a small company [+- a year late in my work]]. No

Re: Plan for 2.0

2009-01-07 Thread Neil Jerram
2009/1/5 Ludovic Courtès l...@gnu.org: 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

Re: Plan for 2.0

2009-01-05 Thread Ludovic Courtès
Hello! Neil Jerram neiljer...@googlemail.com writes: We're clearly moving towards a 2.0 release. Cool! 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

Re: Plan for 2.0

2009-01-05 Thread Neil Jerram
2009/1/4 Neil Jerram neiljer...@googlemail.com: 2009/1/4 David Séverin da...@altosw.be: 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,

Re: Plan for 2.0

2009-01-05 Thread David Séverin
Le Sun, 4 Jan 2009 16:25:47 +, Neil Jerram neiljer...@googlemail.com a écrit : 2009/1/4 David Séverin da...@altosw.be: 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

Re: Plan for 2.0

2009-01-04 Thread David Séverin
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

Re: Plan for 2.0

2009-01-04 Thread Neil Jerram
2009/1/4 David Séverin da...@altosw.be: 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

Re: Plan for 2.0

2009-01-04 Thread Andy Wingo
Hi Neil, On Sat 03 Jan 2009 19:38, Neil Jerram neiljer...@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

Re: Plan for 2.0

2009-01-04 Thread Greg Troxel
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. That seems like a good plan on all counts, plus perhaps period of feature freeze on master, with testing on many OS and architecture variants, with a special

Plan for 2.0

2009-01-03 Thread Neil Jerram
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