Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

CODING STANDARDS POWER RANKING 1st Ed.

Name: One Happy Nigga 2012-07-08 6:34

function/method/variable naming edition

1. fetch_one
2. fetchone
3. fetch-one

.9001 fetchOne
.90001 FetchOne

you = 'faggot' if rank > 9000

Name: Anonymous 2012-07-08 7:08

http://www.oracle.com/technetwork/java/codeconventions-150003.pdf

Of course other languages have different conventions.

Name: Anonymous 2012-07-08 7:34

camelCase rocks.

Name: Anonymous 2012-07-08 8:16

-> is worse than camelcase.

Name: Anonymous 2012-07-08 8:33

common-lisp-style is the best because it's readable and you don't have to use the shift key.

Name: Anonymous 2012-07-08 12:28

>>5
this

Name: Anonymous 2012-07-08 12:35

>>1
That's fine.  You put the ones I use often into the decimal range.

Name: One Happy Nigga 2012-07-08 13:13

>>7

Oh shit nigga my bad. You're still a closet faggot though. Enjoy sucking camel dicks.

Name: Anonymous 2012-07-08 13:26

>>8
lol u fuked up

Name: Anonymous 2012-07-08 13:51

local-variable
*global-variable*
+constant-variable+

Name: Anonymous 2012-07-08 17:17

dUB_Z cHECK_eM

Name: Anonymous 2012-07-08 18:52

I'd use 3 if it was supported.

Name: Anonymous 2012-07-08 19:06

>>11
o shit dude nice fucking dubs

Name: Anonymous 2012-07-08 19:12

Master-Race Tier:

localVariable

(don't use global variables)

GLOBAL_CONSTANT

ClassOrStructName

FunctionOrMethodName

Name: Anonymous 2012-07-08 21:38

>>14
FunctionOrMethodName
M$-tier, lol.

Name: >>15-san 2012-07-08 21:43

>>14
At least not as bad as hdwxOptionalVariableB.

Name: Anonymous 2012-07-08 22:14

Underscores are superior because they are (0) simpler with less rules, and (1) easier for programmers unfamiliar with English grammar.

variable_identifier

function_name (any type of function)

class_identifier

Template_parameter

Name: Anonymous 2012-07-08 22:20

>>17
No, they mess up with scope resolution operators anyway.

cxp_a->weaboo.rst = 1;

Name: Anonymous 2012-07-09 9:18

I've always been a fan of how Go handles variable naming. CamelCase is the standard and the first character denotes if the package should make the function/variable/structure accessible from other packages.
It's a surprisingly good method.

Name: Anonymous 2012-07-09 9:45

10 PRINT "ONLY NEWFAGS USE LOWERCASE"
20 GOTO 10

Name: Anonymous 2012-07-09 12:52

I go by PascalCase for type names because whatever.
camelCase for variable names.
underscores_for_function_names.

I am thinking about switching PascalCase and camelCase though as type names are really more adjectives and variable names really more proper nouns. Underscores for function names make sense because they are more supposed to be descriptions of a process so should read more like a sentence than the other things.

Name: Anonymous 2012-07-09 14:31

check-doubles self

Name: Anonymous 2012-07-09 17:34

Depends on the language. 2 is stupid, though.

Name: Anonymous 2012-07-09 19:53

>>17
Hyphens are easier

Name: Anonymous 2012-07-09 20:45

>>24
to type? just remap the key, underscore to hyphen and vice versa. it's what i've done.

Don't change these.
Name: Email:
Entire Thread Thread List