A backslash in C++
-
I started off my professional programming career using vi as my editor. Ah, for the days of :wq.
-
that really sounds like pain, but it's painfull to deal with IDE bugs and slowdowns too, so maybe you're right :^)
We didn't have IDE's on Unix systems when I started. I'm, what's the word I'm looking for? Oh yes, I'm old.
-
My co-worker was struggling with a bug in an old C++ program.
// Sometimes carry out the work \
if (flag) {
SomeWork();
}SomeWork() was called regardless of the value of
flag. It took her a few hours to find a backslash at the end of the comment.The compilers I've used give a warning in cases like this. JM2B,
Pablo. "Accident: An inevitable occurrence due to the action of immutable natural laws." (Ambrose Bierce, circa 1899). "You are to act in the light of experience as guided by intelligence" (Rex Stout, "In the Best Families", 1950).
-
I started off my professional programming career using vi as my editor. Ah, for the days of :wq.
A good while ago I worked in a department where we did software development on both MSDos and Unix boxes. On the Dos boxes we used a realy good text editor called MultiEdit. One developer asked if I could get him MultiEdit for Unix - I replied no, but said that I couod get him vi for Dos - he nearly punched me!
========================================================= I'm an optoholic - my glass is always half full of vodka. =========================================================
-
We didn't have IDE's on Unix systems when I started. I'm, what's the word I'm looking for? Oh yes, I'm old.
Yup, no argument from here. BTW, IIRC in vi you can write and exit with only three key strokes -
[ESC]ZZ- rather than the cumbersome five of[ESC]:wq[ENTER].speramus in juniperus
-
If you are programmer with not enough background with the language i don't thing that the best practice is to disable the coloring of the text. I think that the language itself it is not so easy to do such practice. And beside that coloring can save you hours of debugging in some cases like this for example. A enough experienced c++ / colorblind programmer can disable the coloring without lowering his or hers productivity.
Microsoft ... the only place where VARIANT_TRUE != true
When you become practised in the art then you simply hold your hands above the keyboard in supplication and the code writes itself out of fear of reprisals. :cool:
speramus in juniperus
-
When you become practised in the art then you simply hold your hands above the keyboard in supplication and the code writes itself out of fear of reprisals. :cool:
speramus in juniperus
-
We didn't have IDE's on Unix systems when I started. I'm, what's the word I'm looking for? Oh yes, I'm old.
-
The compilers I've used give a warning in cases like this. JM2B,
Pablo. "Accident: An inevitable occurrence due to the action of immutable natural laws." (Ambrose Bierce, circa 1899). "You are to act in the light of experience as guided by intelligence" (Rex Stout, "In the Best Families", 1950).
-
I don't - I have "treat warnings as errors" set on my projects to prevent compilation succeeding! :laugh:
Never underestimate the power of stupid things in large numbers --- Serious Sam
-
Oops! It was like this:
// Sometimes carry out the work \
if (flag)
{
SomeWork();
}That's a reason more to use K&R style (or a variation of it)!! :laugh:
-
I don't - I have "treat warnings as errors" set on my projects to prevent compilation succeeding! :laugh:
Never underestimate the power of stupid things in large numbers --- Serious Sam
-
I don't - I have "treat warnings as errors" set on my projects to prevent compilation succeeding! :laugh:
Never underestimate the power of stupid things in large numbers --- Serious Sam
-
I don't - I have "treat warnings as errors" set on my projects to prevent compilation succeeding! :laugh:
Never underestimate the power of stupid things in large numbers --- Serious Sam
-
That's the whole point: if you set "treat warnings as errors" then compilation fails until the warning is fixed. You can't run or test you app until you do.
Never underestimate the power of stupid things in large numbers --- Serious Sam
-
And what about those hard core devs who swear by (instead of at) vi? My point wasn't that Notepad++ supports or does not support colourisation. It's that you can't rely on colourisation to indicate problems.
-
When you become practised in the art then you simply hold your hands above the keyboard in supplication and the code writes itself out of fear of reprisals. :cool:
speramus in juniperus
-
Hey, I like vi. There are parts of it that I wish were available in Visual Studio. dd for instance. Or 10dd to delete 10 lines. Yes, you can do this using other means in an IDE, but they are all more cumbersome.
-
That's the whole point: if you set "treat warnings as errors" then compilation fails until the warning is fixed. You can't run or test you app until you do.
Never underestimate the power of stupid things in large numbers --- Serious Sam
-
I just make sure my code compiles without warnings. If I really cannot avoid a warning, I use a pragma to disable a specific warning, with an explanatory comment.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
