On Feb 7, 7:43 am, Jorgen Grahn <grahn+n...@snipabacken.se> wrote:
I see this class CFoo scheme in a lot of postings
here. Why do people use it, *really*?
...
It provides no information and is just in the way.
It does provide information. The information just isn't of
significant utility, and doesn't belong there. The practice reduces
identifier readability and frustrates the evolution of code, such
that - for example - should CFoo need to be replaced with a
namespace, a programmer may leave the name as CFoo to avoid needing
to change a potentially large or even unreachable body of client
code, after which the 'C' is actively misleading.
Why does anyone do it? I guess because they've been exposed to it
and not worked on the scale of code where the downsides dominate....
Cheers,
Tony