Dear all, How can I have a grammar that matches a terminal of any callable type? Be it a function, function object, or a Boost.Function (specifically). TIA, --Hossein
On 14/01/11 14:08, Hossein Haeri wrote:
Dear all,
How can I have a grammar that matches a terminal of any callable type? Be it a function, function object, or a Boost.Function (specifically).
Hmmm, IIRC proto has a can_be_called metafunction, dunno how far it reaches in term of detection of possible corner cases. BTW Eric, any objection to extract can_be_called to merge in boost.traits ? I think it is really useful externally.
On 1/14/2011 8:32 PM, Joel Falcou wrote:
On 14/01/11 14:08, Hossein Haeri wrote:
Dear all,
How can I have a grammar that matches a terminal of any callable type? Be it a function, function object, or a Boost.Function (specifically).
Hmmm, IIRC proto has a can_be_called metafunction, dunno how far it reaches in term of detection of possible corner cases. BTW Eric, any objection to extract can_be_called to merge in boost.traits ? I think it is really useful externally.
See https://svn.boost.org/trac/boost/ticket/3783 -- Eric Niebler BoostPro Computing http://www.boostpro.com
Hi Joel (or Eric),
Hmmm, IIRC proto has a can_be_called metafunction, dunno how far it reaches in term of detection of possible corner cases.
Can I see its documentations? (I mean something more than what is just in the Appendix.) And, more especially, where is defined?
BTW Eric, any objection to extract can_be_called to merge in boost.traits ? I think it is really useful externally.
Yes, I have to second that. TIA, --Hossein
On 1/14/2011 9:03 PM, Hossein Haeri wrote:
Hi Joel (or Eric),
Hmmm, IIRC proto has a can_be_called metafunction, dunno how far it reaches in term of detection of possible corner cases.
Can I see its documentations? (I mean something more than what is just in the Appendix.) And, more especially, where is defined?
It's an implementation detail, and is not general. There are no docs, and you shouldn't use it.
BTW Eric, any objection to extract can_be_called to merge in boost.traits ? I think it is really useful externally.
Yes, I have to second that.
You must have missed my earlier msg. I filed a feature request for the function_types library and attached an implementation of an is_callable_with_args trait. That's about all I can do. The feature request is 13 months old. Take the issue up with Tobias. -- Eric Niebler BoostPro Computing http://www.boostpro.com
Hi Eric,
Can I see its documentations? (I mean something more than what is just in the Appendix.) And, more especially, where is defined?
It's an implementation detail, and is not general.
I got the same impression when I read about it in the Appendix. But,
There are no docs, and you shouldn't use it.
:)) I need it! I would otherwise need to reinvent wheel!
You must have missed my earlier msg. I filed a feature request for the function_types library and attached an implementation of an is_callable_with_args trait. That's about all I can do. The feature request is 13 months old. Take the issue up with Tobias.
OK, I'll track it from there too. But, I'll need something to get my next version of code go. Cheers, --Hossein
On 1/15/2011 1:23 AM, Hossein Haeri wrote:
Hi Eric,
You must have missed my earlier msg. I filed a feature request for the function_types library and attached an implementation of an is_callable_with_args trait. That's about all I can do. The feature request is 13 months old. Take the issue up with Tobias.
OK, I'll track it from there too. But, I'll need something to get my next version of code go.
Just take the code attached to the feature request and make it an implementation detail of your library. -- Eric Niebler BoostPro Computing http://www.boostpro.com
participants (3)
-
Eric Niebler -
Hossein Haeri -
Joel Falcou