|
I can only dream of achieving such heights. 
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
Yes, we do know PMs have a quite twisted perception of the software development process. 
Veni, vidi, vici.
|
|
|
|
|
Hey man, hats off to vi: it provides syntax colouring as well.
And you can rely on colourization. Well, unless you write something like
for (n=0; n<100; ++n);
{
doSomething();
}
Veni, vidi, vici.
|
|
|
|
|
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).
|
|
|
|
|
Who looks at warnings? nobody that works with me, sadly 
|
|
|
|
|
I don't - I have "treat warnings as errors" set on my projects to prevent compilation succeeding! 
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
People here don't read error messages, so even if i set that they would just ignore
|
|
|
|
|
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
|
|
|
|
|
My old boss once jokingly said that he was still waiting for the "treat errors as warnings" flag. 
The good thing about pessimism is, that you are always either right or pleasently surprised.
|
|
|
|
|
Many programmers use "treat errors as warnings" flag.
|
|
|
|
|
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.
|
|
|
|
|
|
Lol.
Getting information off the Internet is like taking a drink from a fire hydrant.
- Mitchell Kapor
|
|
|
|
|
Priceless. He sure got a lot of down votes for that one!
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
Here was my version: how to write a program[^]
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
haha hilarious, what happened in the end? Did he come clean to his tutor?
|
|
|
|
|
No idea.
I gave him 25 hours to be kind, and then sent the email. He hasn't been back since... 
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
|
haha
I like how he's told that they won't delete anything and he's like "Ok guys tnx at least delete this thread so she won't think I was doing anything wrong".
|
|
|
|
|
I just found this in some ancient C code:
if (number_of_records > 0)
{}
else
{}
I'd love to know what the original programmer was intending to do here because I have to maintain this crap! 
|
|
|
|
|
He was just explaining syntax of if...else to his/her co-programmer. The co-programmer was free to cook anything between these {}.
|
|
|
|
|
There is the code I was looking for! Could you please tell me what file its in now
|
|
|
|
|
Yes, its in a function called read_the_mi_file() in MINSERT.C
If you'd like to take ownership of the whole pile of BS I'll ZIP it up for you..
|
|
|
|
|
It's a long standing game of Code Tennis.
You fill in the "if" part, and send it back for his move on the "else".
Never underestimate the power of stupid things in large numbers
--- Serious Sam
|
|
|
|
|
He had that variable number_of_records sitting around and had to do something with it.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
