cerr << w->core.x << endl ;
Bit by %lf... have you ever been debugging... and doing a
fprintf(stderr, "x=%lf y=%lf\n",
w->core.x, w->core.y);
and spending a looooooooooong time wondering why w->core.xy are 0.0000... and then realize that w->core.xy are integers???!!!???
cerr << "x=" << w->core.x << " "
<< "y=" << w->core.y << endl;
See why they did that... i just hate how long it is... but really is it any longer???
Maybe it is having to get iostream and importing the std::cerr guy and all that.
4 comments:
LOL -- had the %lf happen to me this morning. The compiler caught it and issued a warning, and, fortunately, I noticed. But I know what you mean about the iostream -- seems longer, and I guess that's why people start putting "using namespace std;" all over the place. Seems like it would be nice if C++ had a behavior that said "is there anything that's been explicitly #included that might fit cerr?" But I guess C++ can't tell what's been explicitly included and what hasn't, so we're stuck with "using std::cerr".
looks like i am going to have to make people fill out the funky comment verifier as i am startin' to get spammed
to buy cheap sudafed click
for the best new tires click
to play a Def Lepard mp3 click
I can make cheap meth from sudafed!!! And burn rubber!!! And jam to Def Leo Pard!!!
Post a Comment