Re: methodname ref to overloaded operator

Daniel James <[email protected]>
Newsgroups gmane.comp.lib.boost.documentation
Message-ID <CAHOE3yf3Azds7CeTbSFdeAq4UufX72=fXfYCkmvxU_eL0rqwoQ@mail.gmail.com>
On 21 July 2012 21:34, Eric Niebler <[email protected]> wrote:
> On 7/21/2012 1:16 PM, Daniel James wrote:
>> On 21 July 2012 20:59, Eric Niebler <[email protected]> wrote:
>>> Here's a very small work item for an XSLT hacker with a little time to
>>> kill. (He says wishfully.) I can't refer to an overloaded operator. If
>>> put this in a boostbook xml file:
>>>
>>> <methodname>proto::functional::as_env::operator()</methodname>
>>
>> A test case would help. Try the attached, it's untested.
>
> W00t! That works. I suppose all the operators would need to be handled
> similarly. Do you still need a test case?

Only 'operator()'. It strips of anything that starts with '(', I think
it's trying to deal with things like '<methodname>x::foo(int
y)</methodname>'. A full solution should probably do the same if
there's a '(' after 'operator()'. A test case would be good, I'm
trying to include one for anything new I add - it's hard to work out
what the script is meant to be doing, so it's useful to at least
illustrate what I think it should be doing.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.