FastEddie posted:

No, they're bitwise shifts, because they operate on bits, rather than the boolean interpretation of the collections of bits. I have no idea what a logical shift would be.

floWenoL posted:

No, if the integer is signed and negative, the behavior is implementation-defined.

Plastic Jesus posted:

I came across this a year or two ago:

floWenoL posted:

And compile time is a major bottleneck for large C/C++ programs. Pike's advice might be outdated, but including (non-system) headers willy-nilly is a good way to kill compile performance.

Nahrix posted:

code:

void fillFiles(FILE **file)
{
  ...

  for loop (i iterator)
  {
    [b]*file[i] = fopen(blah);[/b]
  }

  ...
}

Rottbott posted:

I'm surprised people like it so low. My Visual Studio layout on my work PC can fit over 200 columns. Our existing C codebase with parts dating back to 1997 frequently exceeds 100 columns. A limit of 80 would drive me nuts.

sarehu posted:

If you wrote

struct stuff *s = malloc(sizeof(s));

you would also be in better shape.

Xarn posted:

Yep, recursive make means makefile that goes into a subfolder and calls make from there. This breaks deps, paralelization and similar things.

qsvui posted:

A reminder that even the C standards committee decided that VLAs were a mistake and made them optional in C11.

Xeom posted:

Preferably something that can be called hundreds of times a second with little overhead.

Hatsune Mike posted:

In C, I'd be happy doing something like this:

Dren posted:

Hard disagree. cmake is much nicer than a pile of crusty make garbage.

Zopotantor posted:

Floyd's cycle detection algorithm, which every programmer ought to know

Volguus posted:

I always hated begin and end and typing := (although it's easier and clearer to read).

Rocko Bonaparte posted:

My more fundamental problem is I've been doing a lot more OOP for the past ... 20-odd years (drat) and the code reuse monkey on my back is screaming about what I'm doing.

ExcessBLarg! posted:

You shouldn't place functions in headers unless they're inline

rjmccall posted:

Words

His Divine Shadow posted:

C++ code looks so loving incomprehensible to me compared to regular C.

qsvui posted:

chglcu posted:

Especially when sickos put the opening brace on its own line.

roomforthetuna posted:

Sometimes you close and it's an else or the while of a do-while.

roomforthetuna posted:

Yes it still is sometimes an else after a brace, you're just saying you should format that like a maniac. You appear to be suggesting this monstrosity?

code:

if (banana) {
  doStuff();
}
else {
  doOtherStuff();
}