This can be closed.

Not sure. The one warning itself has been fixed, but if it ever comes back, the cryptic message is there again with no help whatsoever about where the warning comes from.

I took a look at this. The code of all files is put into a single variable, therefore without bigger changes it would not be possible to get the file and the line number that causes the warning.

It would be possible to print the code that and make it more obvious. Would that be enough?

The parser should be able to tell the class name, that would be absolutely helpful.

Are this changes okay?

Example output:

** tolua warning: No support for operator =
Code that contains the unsupported operator:
cBoundingBox & operator=(const cBoundingBox & a_Other)

Almost, the output is exactly what I'm after, but it should still go through the warning function, rather than regular print. Please make a PR with such a change, you're just a tiny step away from it :)

Switched to using warning. I used a local variable to build the output together. The function warning would print out two newlines for every line.

Still need to upgrade the tolua subrepo in here...