Hi,
I just released the first version of guile-xmlrpc. This comes from a
module I wrote for tekuti (Andy's blog engine) to be able to support
the MovableType API. It has evolved a bit since then.
If you want to give it a try, in the examples/ directory there's a
server and a client that should ta
Andy Wingo skribis:
> I agree that we would do well to allow bytevectors wherever an argument
> type is a pointer. It avoids an allocation in a very common case
> without changing the expressiveness of the interface or adding
> significant additional overhead.
I find it somewhat inelegant, thou
Hello,
That does sound very useful. The only thing that makes me worried is
On Tue, Feb 5, 2013 at 12:38 PM, Andy Wingo wrote:
> On Thu 17 Jan 2013 11:53, Marco Maggi writes:
> > The other Scheme implementations using a non-compacting
> > garbage collector
>
Do we want to guarant
On Thu 17 Jan 2013 11:53, Marco Maggi writes:
> * Whenever a callout to C accepts a pointer argument: a
> bytevector argument is rejected. Is this not a useless
> complication?
>
> One canwork around it byexplicitly using
> BYTEVECTOR->POINTER, so everything is
Alle lunedì 4 febbraio 2013, Ludovic Courtès ha scritto:
> Richard Braun skribis:
> > On Sat, Feb 02, 2013 at 07:51:38PM +0100, Gabriel Schnoering wrote:
> >> I can't run guile in gdb as there are some error with the garbage
> >> collector.
> >
> > These are probably not errors.
>
> Indeed, you
Hello,
"objc" skribis:
>>> FAIL: tests/alist.test: sloppy-assq not
>>
>> ;;; :242:2: warning: possibly unbound variable `pass-if'
Actually you need to type in just the body of the ‘pass-if’ or
‘pass-if-exception’ forms. Could you try that?
>> ;;; :473:4: warning: possibly unbound variable `de
Hi Ludo,
Some tests as requested.
---
FAIL: tests/alist.test: sloppy-assq not
;;; :242:2: warning: possibly unbound variable `pass-if'
;;; :246:2: warning: possibly unbound variable `pass-if'
;;; :250:2: warning: possib
