<p>I changed groups within Google about two years ago, moving from the build tools group to the speech group. Since then I haven't been as active as I used to be. However I still follow the mailing lists, and try to respond to every patch eventually. I am also planning to make a new distcc release in the next few months.</p>
<p>Over the last couple of months, I have been travelling quite a bit, with most of the time since before Christmas spent not at home. I should have more time available in the next few months.</p>
<p>I am very supportive of efforts to make pump mode work with the boost headers.</p>
<div class="gmail_quote">On Feb 16, 2011 7:44 PM, "Martin Pool" <<a href="mailto:mbp@canonical.com" target="_blank">mbp@canonical.com</a>> wrote:<br type="attribution">> On 16 February 2011 22:51, Alastair Rankine <<a href="mailto:arsptr@internode.on.net" target="_blank">arsptr@internode.on.net</a>> wrote:<br>
>> So as a followup to my last email, I've found a few bugs in the macro processing code in the include_server. This doesn't yet mean that the boost headers can be parsed in a reasonable time, but I'm going to continue to work on it.<br>
>><br>>> I've got a branch here which has fixes and test cases for all the bugs found to date:<br>>><br>>> <a href="https://code.launchpad.net/~arankine/distcc/issue16" target="_blank">https://code.launchpad.net/~arankine/distcc/issue16</a><br>
>><br>>> Briefly, the fixes are as follows:<br>>><br>>> - Handle ## operator immediately following a function-like macro: FOO(bar)##baz<br>>> - Handle spaces between a symbol and parens for a function-like macro invocation: FOO (bar)<br>
>> - Handle spaces in the argument list of a multiple argument macro definition & invocation: FOO(bar, baz)<br>>> - Spaces around the ## operator as mentioned in the previous email: a ## b<br>> <br>> I had a look over them and they look pretty plausible.<br>
> <br>> I don't know if Fergus is very active on this anymore. (I heard a<br>> rumor about Google having switched to a fork of distcc based on their<br>> proprietary infrastructure?) Perhaps you should get commit access if<br>
> you want to work on it.<br>> <br>>><br>>> By the way, In the last email I was trying to float the idea of not populating the value set with verbatim function-like macros. I haven't yet decided whether or not this is a good idea, so I haven't committed it to the branch above.<br>
>><br>>> Very much interested in any feedback.<br>>> __<br>>> distcc mailing list <a href="http://distcc.samba.org/" target="_blank">http://distcc.samba.org/</a><br>>> To unsubscribe or change options:<br>
>> <a href="https://lists.samba.org/mailman/listinfo/distcc" target="_blank">https://lists.samba.org/mailman/listinfo/distcc</a><br>>><br>>><br>> __<br>> distcc mailing list <a href="http://distcc.samba.org/" target="_blank">http://distcc.samba.org/</a><br>
> To unsubscribe or change options:<br>> <a href="https://lists.samba.org/mailman/listinfo/distcc" target="_blank">https://lists.samba.org/mailman/listinfo/distcc</a><br></div>