- 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 3:05:03 PM
> Subject: Re: Val.true and Val.false [Was: XMLRPC] (fr
Hmm, on second thought, I suspect your problem is that you merge
instead of rebase on "git pull". Check that you've got the rebase flag
set to true, i.e. your .git/config should contain something like this:
[branch "7.9"]
remote = origin
merge = refs/heads/7.9
rebas
Yes, looks ok now. Good. :)
> 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.
Recloning sounds overly brutal, but I can't say what's happened in
your case. If it's the usual problem with that the branch head has
moved on the ser
- 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
- 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
Okay, I got it. I just recloned the repo and recommited. 7.8 and 7.9 should
have the patches in now.
> 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
>remote: Commit 65a4850d0c0afba9b89ba4698b728c5224c3ee97 does not contain
>d0344c6c82231970df581550111574da60aa8a84 in its first-parent ancestry.
There's your error. d0344c6 is the current head of 7.9, but you are
trying to push something (65a4850) which is not a continuation from
that point. P
- 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 12:45:02 PM
> Subject: Re: Val.true and Val.false [Was: XMLRPC] (from
- 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 12:45:02 PM
> Subject: Re: Val.true and Val.false [Was: XMLRPC] (from
Thanks for the effort, but it still needs some fixing:
The compat flag is the wrong way. The point with compat is that old
code should continue to work without changes. With this patch it's
still necessary to change some calls to get the old behavior back. (If
you don't like the flag in new code t
- 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]
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
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
>
> > Looks ok, but could you please update the docs accordingly as well?
> >
> > Getting (optional) boolean support when decoding would be nice from a
> > feature and symmetry perspective, but that's not a requirement imo.
> >
> > > In order to backport Val.pmod to 7.8.526, I had to r
Patch for boolean support for Protocols.XMLRPC
--- module.pmod.orig2011-08-31 16:02:19.838058384 -0400
+++ module.pmod2011-09-07 10:17:21.848427570 -0400
@@ -15,12 +15,15 @@
//! Pike @expr{mapping@} is translated to XML-RPC @tt{@}.
//! Pike @expr{array@} is translated to XML-RPC @tt{@}.
18 matches
Mail list logo
