"White space"

[ChuckDickerson]

Originally Posted by virtuald

Why wouldn't you use white space?

It adds too much weight to the robot. Each space = ~0.0001327 oz. Tabs are either 4 or 8 times that depending on your editor settings. Count up all the white space in your code sometime and calculate how much weight it adds.

[swamp_child]

Originally Posted by DeepWater

It adds too much weight to the robot. Each space = ~0.0001327 oz. Tabs are either 4 or 8 times that depending on your editor settings. Count up all the white space in your code sometime and calculate how much weight it adds.

for the same reason we usually don't use comments.

[Bongle]

I love whitespace! If the OP is trying to argue against it, he's in for a surprise if he ever gets a programming job. Even if you can read non-whitespaced code, nobody else can.

Some kids I've mentored in the past didn't use tabs at all, and it was painful to look at. It was impossible to tell, at a glance, when functions started, the scope of loops, etc. It was all either memorization or bracket-counting.

[The Lucas]

This year I found the majority of compilation errors that I helped my students fix were due to mismatched braces (usually with inconsistent indention). Whitespace is good, especially if you want quick help.

Helpful Windriver tip: Select your code and press Ctrl-I to auto indent your code

[basicxman]

Originally Posted by DeepWater

It adds too much weight to the robot. Each space = ~0.0001327 oz. Tabs are either 4 or 8 times that depending on your editor settings. Count up all the white space in your code sometime and calculate how much weight it adds.

I sincerely hope you're joking. Extra code doesn't add any weight.

[Alan Anderson]

Originally Posted by basicxman

Extra code doesn't add any weight.

Right. It's the other way around. The erased state of flash memory is a logic one, so adding code actually removes bits.

[EricVanWyk]

Originally Posted by Alan Anderson

Right. It's the other way around. The erased state of flash memory is a logic one, so adding code actually removes bits.

Bah, the weight savings of a few electrons in flash are nothing. We added a few vandegraph generators to the bot to remove some real electrons!

[billbo911]

Originally Posted by EricVanWyk

We added a few vandegraph generators to the bot to remove some real electrons!

And you wonder why we are getting static charge build up this year.

[writchie]

Originally Posted by Alan Anderson

Right. It's the other way around. The erased state of flash memory is a logic one, so adding code actually removes bits.

Ahhh, but the process of writing a "zero" is done by injecting electrons into the float gate. So a programmed device has the mass of these electrons (which is of course negligible).

[dooey100]

You are missing an option on that poll:

"I can't even read my own code"

[basicxman]

Sorry I didn't specify, adding or removing code does not change the weight!!

Anyways, here's some sample code from my joystick for FTC, this is how I like things whitespaced

while (true) { //whitespace after an important conditional or loop

  getJoystickSettings(joystick); //single linebreak for basic commands and function calling
  setMotors("default"); //double linebreak when another main conditional is about to appear

  if (joystick.joy1_y1 > 40 || joystick.joy1_y1 < -40) { //single linebreak for a final conditional in nests
    motor[motorD] = joystick.joy1_y1; 
  }

}