ous compiler version which required a
statement like that to keep it quiet for some warning? I've seen it in
several different files.
Just curious...didn't know if this was some obscure trick I was unaware of -
other than quieting a compiler to say a variable's unreferenced...
Thanks,
D.J. Stachniak
To me something that is extremely valuable is something like pimpl/compiler
firewall towards not exposing any of your implementation (even when your
data members are private) across a binary boundary. This can be huge in
avoiding an impact when you're patching code, etc. A lot of things like
that
That's the exact reason why I say char *foo is the "right" way to do it. I
think a subject like this even brings a bigger picture topic to light in
that a coding standard might even want to avoid multiple declarations in the
same line/statement for that very reason. As I get "on" in years I tend
As a guy who actually likes C++/STL and sees a lot of value in it, I know
already that 99% of this list disagrees with me - AND I've always been a guy
who types char* foo without even thinking and prefer it...but...truth be
told, I can't with good reason argue against John here and have to agree
wi
