Funny Pictures Thread. It begins again

GasBandit

GasBandit

Staff member
Dei said:
Spoilers, my son was 1 when I got married. :p
Click to expand...
I think you'd actually mentioned this to me before ;)

My favorite part of that was how until we were official married, even though we had a child and were living together, neither of our families let us share a room when we stayed with them on visits.
Click to expand...
Well, they didn't want Samantha to be 14 now, you horny kids :p


When my folks got married, my mother was 19 and my father 21. I, however, didn't come along until my father was almost finished with med school.

(I might have told this story before)

He likes to tell the story about how he was studying for his finals in med school, with a pregnant wife about to give birth already in the hospital from other complications, when he realized that if he bombed this test, he'd have absolutely nothing to show for all his schooling. He never got a high school diploma due to spending his senior year in Australia (military family thing), but got accepted to Rice University without one anyway... but then went to medical school before he finished getting his degree there...

No pressure.
 
GasBandit

GasBandit

Staff member
Dei said:
As hilarious as getting revenge for having a very thin wall between mine and my parents' bedroom would be, so much no.
Click to expand...
Gah, my mom and stepdad used to go at it IN THE LIVING ROOM when they thought my brother and I were asleep. They were not very quiet.

/haunted

Also, saturday mornings, watching cartoons was slightly more irritating for the distraction of the constantly squeaking ceiling. >_<

It's a miracle I'm as well adjusted as I am.
 
Gruebeard

Gruebeard

GasBandit said:
Heh, I was still in college and still technically unmarried (though as-good-as-monogamous, for my part), otherwise, who knows - might have ended up similarly. It was a prompt for life-affirming acts, IIRC.
Click to expand...
Plus, everything was shut down for a couple days, so what else are you gonna do?

Although, for my part, I spent the day after hanging out with an Iraqi-Canadian , discussing who might have been behind the attack.
 
Eriol

Eriol

figmentPez said:
Click to expand...
The semicolon will only stop it from compiling. That's fixable quickly, and only stops you from putting something new into production. So the amount of damage is small.

OTOH, running code can do so much more mayhem. So the block of code on the left is much more dangerous IMO.
 
Eriol

Eriol

stienman said:
Code: 
int will_semicolon_cause_problem = 0;
if(will_semicolon_cause_problem);
{
  printf("Semicolon caused problem");
}
Click to expand...
Fair point. No debate there. I've never seen that before though I acknowledge it's possible, but I HAVE seen this:
Code: 
bool will_semicolon_cause_problem = false; // use bool people!!!
if(will_semicolon_cause_problem)
  // printf("Semicolon caused problem"); // Incident 54321: not needed anymore
do_required_function();
This is IMO much worse. ALWAYS use brackets. You did in your example, I'm just showing a case where people don't. And it's terrible.
 
DarkAudit

DarkAudit

Eriol said:
Fair point. No debate there. I've never seen that before though I acknowledge it's possible, but I HAVE seen this:
Code: 
bool will_semicolon_cause_problem = false; // use bool people!!!
if(will_semicolon_cause_problem)
  // printf("Semicolon caused problem"); // Incident 54321: not needed anymore
do_required_function();
This is IMO much worse. ALWAYS use brackets. You did in your example, I'm just showing a case where people don't. And it's terrible.
Click to expand...
Even more terrible than stealing 40 cakes.

For @Eriol:

The natural response to anyone saying it's terrible. :)
 
Denbrought

Denbrought

Eriol said:
Fair point. No debate there. I've never seen that before though I acknowledge it's possible, but I HAVE seen this:
Code: 
bool will_semicolon_cause_problem = false; // use bool people!!!
if(will_semicolon_cause_problem)
  // printf("Semicolon caused problem"); // Incident 54321: not needed anymore
do_required_function();
This is IMO much worse. ALWAYS use brackets. You did in your example, I'm just showing a case where people don't. And it's terrible.
Click to expand...
Bless linters. Ain't no bracketless crap making it through our StyleCop (ternaries excepted).
 
strawman

strawman

Eriol said:
This is IMO much worse. ALWAYS use brackets. You did in your example, I'm just showing a case where people don't. And it's terrible.
Click to expand...
I agree except in one narrow case...

...where I have a lot of little tests that each only do one thing, and the rule is that the function must appear on the same line as the if:

Code: 
if(something) dofunction1();
if(somethingelse) dofunction2();
This resolves the concern you demonstrated where the if might suddenly apply to the next line, since the if and its action are on the same line. So brackets always with the only exception being when the entire if statement resides on one line. That said, it's not really that much more work nor terribly visually distracting to add the brackets:

Code: 
if(something) {dofunction1();}
if(somethingelse) {dofunction2();}
But it's really annoying when someone tries to use a new toy they just learned about:

Code: 
if(something && dofunction1());
if(somethingelse && dofunction2());
Convert it to the wrong language or use the wrong compiler option and suddenly everything breaks! Of course, that can be shortened to simply

Code: 
something && dofunction1();
somethingelse && dofunction2();
But most sane compilers will at least warn you when you don't have a left value.

 
Denbrought

Denbrought

stienman said:
I agree except in one narrow case...

...where I have a lot of little tests that each only do one thing, and the rule is that the function must appear on the same line as the if:

Code: 
if(something) dofunction1();
if(somethingelse) dofunction2();
This resolves the concern you demonstrated where the if might suddenly apply to the next line, since the if and its action are on the same line. So brackets always with the only exception being when the entire if statement resides on one line. That said, it's not really that much more work nor terribly visually distracting to add the brackets:

Code: 
if(something) {dofunction1();}
if(somethingelse) {dofunction2();}
But it's really annoying when someone tries to use a new toy they just learned about:

Code: 
if(something && dofunction1());
if(somethingelse && dofunction2());
Convert it to the wrong language or use the wrong compiler option and suddenly everything breaks! Of course, that can be shortened to simply

Code: 
something && dofunction1();
somethingelse && dofunction2();
But most sane compilers will at least warn you when you don't have a left value.

Click to expand...
In those cases I tend to favor
Code: 
if(something) { dofunction1(); }
if(somethingelse) { dofunction2(); }
as a compromise.
 
fade

fade

Staff member
In my experience, syntax based bugs are the easiest to fix anyway. The insidious ones are the ones where the code runs, doesn't crash, and gives you an answer that's almost--but not quite--right. You could pour months into those.
 
You must log in or register to reply here.
Top