Wow a real member if the gogo's, posting with us!

Cassandra, but the only reason no one believes her is because she can't stop pretending to be joking to diffuse tension created by her dire warnings

Go ahread and punch these in to ur 3d printer

🍇🍉🍊🍓

Lucky for me this is a fairly simple job; i just had to adjust and clean+lube the chain on my bike and I didn't get to it before the sun went down.

It is but I think it's nice to be able to do it on my own so I kind of enjoy the hassle.

Number1FlabberghasterFan

Why the HELL isn't it called copost then 😡😡😡

Over? I 'ardly know 'er.

I'm watching some fireflies

I'll do it later

Thank you I will tell everyone I can

Sorry, bowser. Mario is at a different castle

The DRY principle says that if you write something more than once you should refactor it. Here I see you used () in two places; that can be a macro, to ease readability.

OK so this is kind of a pain in the neck to do a lot of times but sometimes you can get the output if the C preprocessor.

Then through careful editing, you can kind of figure out what it's turning in to.

int main(...) {
   WEIRD_MACRO(1, 2);
}

Then you could just put comments above and below it, and run cpp -I/all/include/directories main.c

It will tell you the final output and also have debugging garbage about where each thing expanded from.

Not ideal, and also in a big project that uses a complex build tool it can be incredibly hard to get the cpp args, but it can help.

Mismanage it straight into the ground.