> > OK. Another option is to use __func__ which is always correct.
> Please definatly use __func__. With that ok benno too.
I like __func__ where it makes sense, but often developers consider
"i've shown an obscurely named function that i know" to be a solved
problem, and then don't show a good explanation that a user can deal
So always step back and think: Let's say the person doesn't have the
source tree or the ability to read. Can they determine their next
Often times __func__ is not an improvement, because it can be used
like a crutch.