"Rob Stewart" <stewart@sig.com> wrote in message:
From: "Jonathan Turkanis" <technews@kangaroologic.com>
<Arturo_Cuebas@bpmicro.com> wrote in message:
that than the function-signature form. Consider that the return type can have a super-long name:
whatever_cast <long_name_templatized_type<unsigned long, unsigned char> (char)> (&P::f)
True, but in my personal experience this happen less often then long class names.
What about when the return type is a typedef in the class with a long name or is unutterable? (The latter often happens with complicated metaprogramming expressions.)
Sure, I've written plenty of functions like that. I guess I don't bind them very often, for some reason. Anyway, I'm now convinced the return type should be dropped. Jonathan