/tg/Station 13

We don't have much of a coding style definition, especially when it comes to naming things.

I generally use whatever the current file is using but I would suggest implementing a coding style that makes variables and functions as ONE of these:
1. clown_has_aids
2. clownHasAids
3. ClownHasAids
Depending on which the maintainers want to adopt, it's just kind annoying to see SpinAnimation() and change_number_of_hands exist at the same time and for new code we can nip it in the bud.
This wouldn't be an overnight change.

Just wait until you get all 3 of the above ClownHasAids variations doing different things.

Saegrimr wrote:Just wait until you get all 3 of the above ClownHasAids variations doing different things.

The idea is to pick one of those styles, not all three as is the current situation to prevent this and other annoyances.

Dax Dupont wrote:

Saegrimr wrote:Just wait until you get all 3 of the above ClownHasAids variations doing different things.

The idea is to pick one of those styles, not all three as is the current situation to prevent this and other annoyances.

--The joke->



Your head

Usually I just go with

procs: CapsPerWord

var: nocapsperword

I don't think it's worth the bikeshed and arguing about which style is superior to ever enforce though.

ClOwNhAsAiDs--var for loop iterator.

The most common i've seen is name_of_thing for both procs and vars.

>More than one worded vars

Hey man. Stop that.

Armhulen wrote:>More than one worded vars

Hey man. Stop that.

i normally do_things_like_this which tendsToAnnoyOthers andThenIForgotWhichStyle I'm_using_so_I RandomlySwitchTheThree becauseIAmJustThisWay
that being said i normally try_to_do_it_like_this if i don't forget.