Persistently find same error with operator=, copy constructor, assignments, declaration matches/mismatches/candidates

  • I WONDER if the DevC++ compiler was updated silently... I do not remember having such problem but now I persistently get the same error message showing no matches then showing the correct candidates matching the written code...

    I use an ad hoc makefile for the project, so the IDE is no good to set compiling switches. Would there be a combination of switches that makes the compiler lose sight of the declarations and not find what it has under the nose?

    I would like a quick solution to avoid spending time experimenting with switch combinations.

    • I am using templates and pointer to member functions, but problem is in temporary objects and copy constructors.