Re: r6rs library documentation

> Sounds great to me, though Brian & Neil can always come in to correct me > :) Done! See commit ea28e981342fd1d381e489e57cddde97eb390442. In addition to the main .texi payload, I adjusted the formatting on some of your initial paragraphs and removed the descriptions of the base and composite li

Re: Troubles with Objcode and Storing JIT Pointers

Hi Andy, That sounds excellent. If I may ask, do you already have patches or a git branch that adds this slot? If so, what are you doing about the embedded objcode issue? (Changing the bytecode to leave room for it, or hiding the slot in the C code?) If not, why don't I just write that up first a

Re: when to #:replace

On Mon 21 Jun 2010 23:54, l...@gnu.org (Ludovic Courtès) writes: > Merry Solstice! > > Andy Wingo writes: > >> On Sun 20 Jun 2010 23:29, l...@gnu.org (Ludovic Courtès) writes: >> >>> Hi! >>> >>> Andy Wingo writes: >>> A: #:replace. Presumably the user knows what she is doing when she

Re: guile prolog benchmark

Hello, Sounds fun. Is the Prolog-on-Guile code available on-line? Thanks, Ludo’.

Re: when to #:replace

Merry Solstice! Andy Wingo writes: > On Sun 20 Jun 2010 23:29, l...@gnu.org (Ludovic Courtès) writes: > >> Hi! >> >> Andy Wingo writes: >> >>> A: #:replace. Presumably the user knows what she is doing when she >>> uses your module. If she really cares she can change the duplicate >>> bind

Re: Troubles with Objcode and Storing JIT Pointers

Hi Noah, On Mon 21 Jun 2010 20:19, Noah Lavine writes: > I don't know where to store the JITed code. The 2.2 branch probably will add a slot to objcode objects for native code. If you want to do this, that's fine. Otherwise if you want 2.0 compat, use an object property, or equivalently, a weak

Re: when to #:replace

On Sun 20 Jun 2010 23:29, l...@gnu.org (Ludovic Courtès) writes: > Hi! > > Andy Wingo writes: > >> A: #:replace. Presumably the user knows what she is doing when she >> uses your module. If she really cares she can change the duplicate >> bindings resolution mechanism to disallow such impor

Re: r6rs library documentation

Heya, On Sun 20 Jun 2010 23:23, Julian Graham writes: >> I think that Neil would probably have the most useful feedback, as I >> think he has the most global view of the manual. I am inclined to think >> that the level of detail is appropriate, though I imagine that Neil and >> Brian are cringin

Troubles with Objcode and Storing JIT Pointers

Hello all, I have hit a snag in my attempt to add a JIT backend to Guile: I don't know where to store the JITed code. There was a discussion of this a few weeks ago in which it was decided to try to make a simple and quick JIT engine that would be invisible to Scheme, hoping to eventually make a

guile prolog benchmark

Hi, I've come pretty far in writing a parser for prolog. It's a PEG parser without packrat and interestingly it is done by doing a simple modding of a more standard match construct. The parser is custamizable and it is pretty easy to add new user operators for prolog as you can in e.g. gnuprolog.