----- Original Message ----
> From: "Martin Stjernholm, Roxen IS @ Pike developers forum"
><10...@lyskom.lysator.liu.se>
> To: pike-devel@lists.lysator.liu.se
> Sent: Sun, September 11, 2011 2:00:16 PM
> Subject: Re: Val.true and Val.false [Was: XMLRPC] (from p...@roxen.com)
>
> > Actually, I don't think it is necessary that decode_call take the
> > flag, because if you don't pass in any Val objects, then everything
> > will be an int anyway. It currently isn't possible to encode boolean
> > unless you use Val, so if you need to, you will need to use the new
> > features.
>
> Sounds like you're talking about encode_call, and you're right in that
> case. However, decode_call takes an xml string and returns a Call
> object, so it could also benefit from the new decoding feature. I
> believe decode_call is intended for incoming calls when one implements
> an xmlrpc server.
>
Yes, you are absolutely right there. I was just going through all the method
calls the were referenced from client, not any others that were referenced
externally. I now have all decode* methods accepting the boolean flag.
Since re-cloning 7.9 my commits are going fine. I don't know when it got off,
but it seems to be good now, thanks.
