unresolve overloaded function

Code:

---

find_if( v1.begin( ), v1.end( ),
                    not1(bind2nd( mem_fun_ref( &string::find) , string("bleh")) ));

---

I keep getting compiling error for that statement above because string::find is overloaded and the compiler can't resolve which version to use. Does anyone know how to use it without having to static_cast it?

Edit:
I wrote a functor to incapsulate the value being compared to

Code:

---

struct strFind: private std::string
{
  strFind(std::string in) : std::string(in) {}
  bool operator() (const std::string & input) const
  {
    return !compare(input);
  }
 
};
...
int main()
{ ...
pos = find_if( v1.begin( ), v1.end( ),strFind("pearly") );
}

---

wonder what's the limit of this method is.

You don't. As in, you can't. Not without a cast or an intermediate function.

EDIT:
It's one way. Deriving from the standard library classes is generally frowned upon though, since they don't have virtual destructors. A better way would to use composition instead as you can do the entire operation via std::strings public interface:

Code:

---

struct strFind
{
  std::string needle;
  strFind(const std::string& in) : needle(in) {}
  bool operator() (const std::string & input) const
  {
    return needle == input;
  }
 
};
...
int main()
{ ...
pos = find_if( v1.begin( ), v1.end( ),strFind("pearly") );
}

---

Quote:

---

Originally Posted by adeyblue

You don't. As in, you can't. Not without a cast or an intermediate function.

EDIT:
It's one way. Deriving from the standard library classes is generally frowned upon though, since they don't have virtual destructors. A better way would to use composition instead as you can do the entire operation via std::strings public interface:

Code:

---

struct strFind
{
  std::string needle;
  strFind(const std::string& in) : needle(in) {}
  bool operator() (const std::string & input) const
  {
    return needle == input;
  }
 
};
...
int main()
{ ...
pos = find_if( v1.begin( ), v1.end( ),strFind("pearly") );
}

---

---

Thanks for the advice adeyblue. You are right about inheriting from the string class. that just makes the problem more complicated than it should be.