Re: port-for-each vs lazy sweep

2007-08-25 Thread Han-Wen Nienhuys
Kevin Ryde escreveu: > I've struck, in 1.8, port-for-each passing a freed cell to its iterator > func. Eg. "guile -s foo.scm" on Hi, Please see the patch attached. Comments welcome. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen diff --git a/libguile/fports.c b/libgu

Re: Improved (and faster) reader

2007-08-25 Thread Andy Wingo
Hi Ludovic, On Sat 25 Aug 2007 10:23, [EMAIL PROTECTED] (Ludovic Courtès) writes: >> By the way, what does that option actually do. The manual just says >> "Copy source code expressions", which doesn't leave me any the wiser. > > This has to do with unmemoization when debugging: a copy of the >

Re: Switching to Git?

2007-08-25 Thread Han-Wen Nienhuys
Greg Troxel escreveu: > The more serious problem with guile is a lack of focus on timely, stable > releases usable by people who want to integrate it. Plus backwards > compatibility so that people that do integrated it have very little > grief, and the current slib mess. I have switched from CVS

Re: Switching to Git?

2007-08-25 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] escreveu: > If there must be a switch, I'd also say that subversion is probably the best > way to go. > Less culture shock for long time cvs users. Windows people aren't left out. > Guile doesn't > really need the massively distributed model that the Linux kernel requires. A

Re: port-for-each vs lazy sweep

2007-08-25 Thread Han-Wen Nienhuys
Kevin Ryde escreveu: > (This got me wondering why there's a port table anyway, instead of > independent objects with say a weak hash table for the "list of all > ports" needed by port-for-each and flush-all. Historical reasons I > suppose.) I'm hacking at a patch to junk the table for a weak hash

Re: Switching to Git?

2007-08-25 Thread Han-Wen Nienhuys
Andy Wingo escreveu: >> How about switching from CVS to Git [0]? > > The advantages you list are compelling. It is especially good that > savannah supports git. I have only two points to counter: (1) git sucks > to use (but somehow many people seem to manage), and (2) git does not > work on window

Re: Switching to Git?

2007-08-25 Thread Han-Wen Nienhuys
Dan McMahill escreveu: > Another project I'm on has switched to git from cvs and I'm bringing up > the rear in terms of trying to learn the tool enough to use it without > making a mess of things. My biggest complaint, aside from having to > learn another tool, is that git is not really a lightwei

Re: Switching to Git?

2007-08-25 Thread Han-Wen Nienhuys
Kevin Ryde escreveu: > [EMAIL PROTECTED] (Ludovic Courtès) writes: >> How about switching from CVS to Git [0]? > > I would say no. All these other revision systems seem to come and go, > but their supposed features rarely seem to justify the learning curve > (the frequently steep, time consuming,

Re: Switching to Git?

2007-08-25 Thread Han-Wen Nienhuys
Ludovic Courtès escreveu: > Han-Wen did a full import of the CVS history into Git some time ago [1]. > Note that it preserves tags and branches. This Git repository is kept > in sync with CVS using a cron job that runs on Han-Wen's machine. Note that I messed up the name conversion in the histo

Re: Improved (and faster) reader

2007-08-25 Thread Ludovic Courtès
Hi, Kevin Ryde <[EMAIL PROTECTED]> writes: > By the way, what does that option actually do. The manual just says > "Copy source code expressions", which doesn't leave me any the wiser. This has to do with unmemoization when debugging: a copy of the unmemoized expression is attached to the sourc

Re: Gnulib support

2007-08-25 Thread Ludovic Courtès
Hi, Kevin Ryde <[EMAIL PROTECTED]> writes: > The problem is if other libraries do the same thing, ie. put an > strcasecmp in. I expect you get clashes that'd stop an application > using certain combinations of libraries, or getting mis-detections of > what's available where, etc. > > For namespa