On Behalf Of Peter Dimov Subject: Re: [boost] Re: [named_params] timing trivia and some comments
David Abrahams wrote:
"Matthew Hurd" <matt@finray.net> writes:
Why would I want to do this? I would like to use this approach as a way for inserting an intermediary function. Specifically, I would like to call f<direct>(x,y) and have the direct representation called or f<marshal, destination>(x,y) and have an intermediary serialize the params into a block and send it off on a transport where a representation along the lines of f<marshal, source>(x,y) would accept the block in some infrastructure somewhere else. f<queue_for_processing_in_a_thread_pool>(x,y) fits this model too.
Any thoughts?
I guess my first thought is: "Whaa??? What does any of the above have to do with a named parameters library?"
And then I think: "OK, he wants something that mates the serialization library from Robert Ramey with the new tuples (fusion) from Joel de Guzman".
Conceptually, I think that he wants to serialize a boost::function<>. My advice is "don't bother". I use shared_ptr<Command> for serializeable polymorphic functions.
Not too concerned about this as a simple id association gives me what I need for IPC. I just prefix the associated id to the message. Lots of options for this, just need to pick one. For a local call I'm hoping the mechanism will make the function call implicit and then there will not be a need for a function<> or shared_ptr <> indirection. Thanks for your thoughts. Appreciated. Regards, Matt Hurd _______________________ Susquehanna Pacific P/L hurdm@sig.com +61.2.8226.5029 _______________________ 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.