Functor with recursive call

Discussion in 'C++' started by A, Jan 29, 2014.

  1. A

    A Guest

    I have a functor which looks like this:

    struct TLocalRecursiveF
    void operator()(int *P1, std::vector<TStruct*> &S1)
    this->operator()(P1, S1);
    } RecursiveF;

    RecursiveF(P0, S0);

    Now, ignore for a sec the meaninglessness of this functor. In reality it is
    a tree node builder.
    It works fine but I am wondering, is this prefered to doing something like

    struct TLocal
    static void RecursFunc(int *P1, std::vector<TStruct*> &S1)
    RecursFunc(P1, S1);

    TLocal::RecursFunc(P0, S0);

    Is one version preferred over another or faster over another?
    A, Jan 29, 2014
    1. Advertisements

  2. A

    A Guest

    As I've seen that some use struct variables to simulate parameters, I am
    actually asking, is that preferred to the way I passed parameters e.g.


    in a recursive part of the call.
    A, Jan 29, 2014
    1. Advertisements

  3. A member function has a hidden argument - the object for which it's
    called. If your function has no particular need for the object, making
    it 'static' will mean tiny savings in both stack size use during
    recursion and performance. Most likely you won't notice it, really. As
    always the advice is to measure it before making a decision.

    Functors have a very specific trait - they satisfy a requirement to be
    "callable", which makes them useful with standard algorithms like
    'for_each'. In that sense the alternative to a functor is not a struct
    with a static member function, but a stand-alone function. The functor
    is really only needed when it has a *state*. A stand-alone function
    usually doesn't.

    Victor Bazarov, Jan 29, 2014
  4. I would prefer the one that most closely matches the requirements at
    hand and is most clear and simple to understand.

    The requirements are however not obvious.

    If you need local state then a non-static member function might be it,
    but I would prefer a named one rather than operator(), unless this
    object has to be passed to other code as a functor.

    Otherwise the static member function is good.

    You might alternatively consider a named namespace level function placed
    in e.g. a `detail` namespace.

    Or if this is in a (outer) class, just an ordinary but non-public member
    function of that class, instead of doing everything locally, even if in
    a sense that is like polluting the class scope with the implementation
    details of one of its member functions.

    A local lambda would run into the problem of expressing the recursion,
    which would necessitate either a local struct or accessing an outside
    reference to the lambda (e.g. a `std::function` instance), so that would
    just be more complication, not less. I think.

    Summing up, one of the four first. ;-)

    Cheers & hth.,

    - Alf
    Alf P. Steinbach, Jan 29, 2014
  5. A

    A Guest

    thank you guys for your most excelent answers!
    A, Feb 3, 2014
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.