Re: [PATCH] Fix the R6RS exact-integer-sqrt and import into core guile

l...@gnu.org (Ludovic Courtès) writes: Why do you think the C interface should be kept internal? Most of the core arithmetic procedures provide public C interfaces. Why should exact-integer-sqrt be treated differently? Because: 1. I think we shouldn’t augment the C API unless strictly

Re: [PATCH] Fix the R6RS exact-integer-sqrt and import into core guile

Hello,  1. I think we shouldn’t augment the C API unless strictly necessary,     because the idea is to write Scheme, not C, and because of the     maintenance cost. Why would we not want to augment the C API? It seems like a natural complement to augmenting the Scheme API, since Guile is a

Re: [PATCH] Fix the R6RS exact-integer-sqrt and import into core guile

l...@gnu.org (Ludovic Courtès) writes: 1. I think we shouldn’t augment the C API unless strictly necessary, because the idea is to write Scheme, not C, and because of the maintenance cost. At the risk of repeating myself: The main attraction of using libguile for me is the fact

after-gc-hook recently broken for bdwgc 7.2alpha CVS

Sometime between 2.0.0 and current stable-2.0, after-gc-hook has been broken on my system: FAIL: gc.test: gc: after-gc-hook gets called. Both 2.0.0 and current stable-2.0 are built and linked with bdwgc 7.2alpha from CVS, circa 2011-03-27. This on gNewSense metad/mipsel (slightly modified Debian