- Original Message
> From: "Martin Stjernholm, Roxen IS @ Pike developers forum"
><10...@lyskom.lysator.liu.se>
> To: pike-devel@lists.lysator.liu.se
> Sent: Sat, September 10, 2011 4:15:02 PM
> Subject: Re: Val.true and Val.false [Was: XMLRPC] (from p...@roxen.com)
>
> How tiresome
How tiresome. :P
Now I see the magic_zero thingy is a workaround for the same thing. It
wasn't the wisest choice to disregard any false value like that in the
parser.
I think the best solution would be to fix Parser.XML.Simple.parse to
use UNDEFINED as "disregard" value instead, since the current
- Original Message
> From: "Martin Stjernholm, Roxen IS @ Pike developers forum"
><10...@lyskom.lysator.liu.se>
> To: pike-devel@lists.lysator.liu.se
> Sent: Sat, September 10, 2011 12:30:11 PM
> Subject: Re: Val.true and Val.false [Was: XMLRPC] (from p...@roxen.com)
>
> The patch i
Okay I'll take care of that this afternoon.
Sent from Yahoo! Mail on Android
The patch in decode() is good, but it isn't backward compatible since
old code might expect the integers 0 and 1 for booleans. This is what
we discussed earlier on whether or not to make the boolean objects
int-like.
As I said earlier, I suggest an optional flag to Client/AsyncClient to
enable the
