Re: doc libdir and C code modules

2006-02-04 Thread Neil Jerram
Kevin Ryde <[EMAIL PROTECTED]> writes: > I added the words below to the manual as the last subsection in > "Dynamic Libraries", to encourage packages to use libdir. I don't > want to re-open the can of worms about versioning and stuff, this is > intended just to describe the present situation. V

Re: [PATCH] `try-module-autoload' and `current-reader'

2006-02-04 Thread Neil Jerram
[EMAIL PROTECTED] (Ludovic Courtès) writes: > Hi, > > Neil Jerram <[EMAIL PROTECTED]> writes: > >> But that would still bring in a start-stack and so change backtraces, >> so I'd prefer not. > > Oh, right. > >> I really think with-fluids is the way to go. If you agree, I'll make >> this change in

Re: [PATCH] Inlining `scm_is_pair ()'

2006-02-04 Thread Kevin Ryde
Marius Vollmer <[EMAIL PROTECTED]> writes: > > I just put scm_is_pair into inline.h, using our existing inlining > machinery that should be portable enough. Maybe scm_is_eq too (picking up scm_is_true and scm_is_false at the same time). ___ Guile-devel

Re: Backtrace and enhanced catch

2006-02-04 Thread Neil Jerram
Kevin Ryde <[EMAIL PROTECTED]> writes: > Neil Jerram <[EMAIL PROTECTED]> writes: >> >> The spec for catch's pre-unwind-handler would be that it can exit >> either normally or non-locally. If it exits normally, Guile unwinds >> (dynamic context + stack) and then calls the normal (post-unwind) >> h

Re: Backtrace and enhanced catch

2006-02-04 Thread Kevin Ryde
Neil Jerram <[EMAIL PROTECTED]> writes: > > The spec for catch's pre-unwind-handler would be that it can exit > either normally or non-locally. If it exits normally, Guile unwinds > (dynamic context + stack) and then calls the normal (post-unwind) > handler. If it exits non-locally, that exit det

doc libdir and C code modules

2006-02-04 Thread Kevin Ryde
I added the words below to the manual as the last subsection in "Dynamic Libraries", to encourage packages to use libdir. I don't want to re-open the can of worms about versioning and stuff, this is intended just to describe the present situation. 5.16.4.4 Compiled Code Installation ..

Re: Branching for 1.8 on 2006-02-05

2006-02-04 Thread Rob Browning
Kevin Ryde <[EMAIL PROTECTED]> writes: >> (What we have in the 1.8 branch is not immediately the 1.8.0 release, >> but should be very close.) > > Do you really want to branch at all? For what it's worth, I'd say there a benefit to branching as late as possible. If there aren't any items waiting