A backslash in C++
-
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.
-
Oops! It was like this:
// Sometimes carry out the work \
if (flag)
{
SomeWork();
}That's a lousy attempt at obfuscation. Here's a real professional at work: IOCCC[^]. (That is a full hardware emulation of a 1980's PC hardware (much more info in the other files in this folder[^]. Some top aspects: It is 4043 bytes long (half an 8086). "It manages to implement most of the hardware in a 1980’s era IBM-PC using a few hundred fewer bits than the total number of transistors used to implement the original 8086 CPU." (edited for spelling)
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
That's a lousy attempt at obfuscation. Here's a real professional at work: IOCCC[^]. (That is a full hardware emulation of a 1980's PC hardware (much more info in the other files in this folder[^]. Some top aspects: It is 4043 bytes long (half an 8086). "It manages to implement most of the hardware in a 1980’s era IBM-PC using a few hundred fewer bits than the total number of transistors used to implement the original 8086 CPU." (edited for spelling)
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
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.
-
-
Heh. I am not all that used to Vi(m), but this extension seems to be quite powerful.
<voice type="Ebeneezer Scrooge"> Bah. dumb bugs </voice>
