POST THEM CFLAGS

IT'S BEEN A LONG TIME SINCE THE LAST DISCUSSION WE HAD ABOUT THIS...

>>38
This is what c programmers actually believe

>>35
You are a retard. This linker flag prevents packages from breaking every other library update by linking only to libraries that are actually used. Especially useful in large programs that use shit like pkgconfig at compile time, which usually brings in twice the libraries the program normally needs.

>>37
-Werror is counter-intuitive to programming, because neither of these sentences is true:
- warnings always correspond to actual errors in ones source
- source for which no warnings are issued is correct

>>43
IHBT.

>>43
Why?

>>43
Uhh, the compiler authors are giving errors found during the compilation process. I fail to see how that's counter-intuitive.

>>46
I remember gcc used to BAWWW about this:

while(a=*i++)

Some sort of "suggest parentheses around = used in boolean expression" warning. But the code is perfectly fine, there is no error there.

>>47
That would be -Wall, not -Werror, and it would generate a warning, not an error. It would still compile just fine.

>>48
not -Werror
would generate a warning, not an error
IHBT 8/10

>>27
What, you don't like abusing cats?

>>47,48
Some sort of "suggest parentheses around = used in boolean expression" warning.
suggest parentheses around = used in boolean expression
parentheses around =
Did you try actually following the instructions?

while ((a=*i++))

This is a very good warning; the extra parentheses are sortof ugly, but the tradeoff is helping you catch = instead of == 100% of the time. You get used to them and it helps readability afterwards. Actually it's frustrating that Apple doesn't ever build -Wall, because all Objective-C documentation code, templates, etc. suggests a shitload of these, like this idiom in every fucking class:

- (id)init {
  if (self = [super init]) {
    // some shit
  }
  return self;
}

with the obvious warning around the assignment again. Go ahead, create a project template in Xcode, turn on -Wall, and enjoy the warnings. I fucking hate Objective-C.

>>51
Maybe if you had better eyes and/or font you could tell the difference between = and ==. I've written over 9000 lines (seriously) of C and have yet to make that mistake.

>>52
Yeah, I call bullshit on that. Everyone has made this mistake repeatedly, especially when learning a new language. Maybe you think haven't made it because it typically manifests in obvious ways, so you find the error, correct it quickly, and just forget about it; but you've absolutely made it.

I've written over 9000 lines (seriously)
You sound like MDickie. You're anon, what do you have to brag about? Any career programmer easily writes this many lines in a few months/years time.

>>52
wow over 9000 u must be an expert!! i can't someone has written so much

>>52
i've written over 9000 lines just while learning C by working through K&R.

Newer Posts

---

Don't change these.

Name:		Email:
Entire Thread Thread List