On Behalf Of David Abrahams Subject: [boost] Re: [named_params] timing trivia and some comments

...

"Hurd, Matthew" <hurdm@sig.com> writes:

...

...

I guess my first thought is: "Whaa??? What does any of the above have to do with a named parameters library?"

Pretty much nothing. I just like the named_params style of interface and wanted to adopt the approach.

I want to build a mechanism where it is easy to build an interface to a function / functor than can have a policy that allows it to be a normal function or something else such as a function in worker pool or a remote function.

My desire is to make it easy to represent a function and keep this orthogonal to whether it remote, pooled or local via a policy.

You're describing boost::function<...> now.

Nearly, yep. I just want the cool named and default parameters with support for iteration / recursion over the parameters with a bit of introspection.

...

For some of the mechanisms I actually would like names for the parameters to help fulfil a protocol requirement, thus the desire for introspection on the names and a look into your neat library.

So put a named-param front end on a boost::function (?)

OK, I'll take your advice and have a look at doing this. I'll also have a think about if I can find a way to generate the alternative functions using a class generation approach instead of macros later too. Thanks Dave, Regards, Matt Hurd IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.