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

CamelCase

Name: Anonymous 2009-05-19 16:06

WhoTheFuckThoughtThisIsAGoodIdea?

It's an unreadable mess. No real programmer would use that shit.

Name: Anonymous 2009-05-19 16:19

/thread

Name: Anonymous 2009-05-19 16:34

It doesn't look so bad WithAProportionalFont.
Also, nobody uses that many words for identifiers. Aside from JAVA programmers.

Name: Anonymous 2009-05-19 16:34

Real_Programmer_Use_Camel_Space

Name: Anonymous 2009-05-19 16:37

alternaCAPSisTHEbestWAYtoNAMEtheVARIABLES

Name: Anonymous 2009-05-19 16:41

Please use underscores to separate words in a name, so that the Emacs word commands can be useful within them.

gnu_style_is_the_standard!

Name: Anonymous 2009-05-19 16:42

go back to /g/

Name: Anonymous 2009-05-19 16:42

M-x glasses-mode

Name: Anonymous 2009-05-19 16:48

L337v@r!@8|3~@^^E5

Name: Anonymous 2009-05-19 17:44

HaXXeRCaSeiSTHeSTaNDaRD

Name: Anonymous 2009-05-19 17:50

this_IsTheStandard_inPHP_orSoIt_seems();

Name: Anonymous 2009-05-19 17:54

>>6
Please use underscores to separate words in a name, so that the Emacs word commands can be useful within them.
This may surprise you, but c-subword-mode.

Name: Anonymous 2009-05-19 18:21

[code](lisp\ spaces\ are\ the\ standard\ !)[code]

Name: Anonymous 2009-05-19 18:23

>>13
> ぬるぽ
ガ！！

(lisp\ spaces\ are\ the\ standard\ !)

Name: Anonymous 2009-05-19 18:31

>>3
Yeah, the real problem is stupid verbose languages and stupid verbose programmers that leads you to stuff like:

StupidLongTypeName stupidLongVarName = new StupidLongSubTypeName(anotherStupidLongVarName, yetAnotherStupidLongVarName);
And then they consequently fail to stick to 76 characters per line causing me to [spoiler]Rage!11!! and[/spoiler] question their suitablity for the enterprise.

Name: Anonymous 2009-05-19 18:33

>>15
76 characters per line
Why not 80?

Name: Anonymous 2009-05-19 18:59

>>16
I suppose 76 makes it easy to send the code in an email with the Quoted-Printable encoding¹. Though your mail client should do that for you anyway.

References                            
¹ Freed, N.; Innosoft; Borenstein, N.; RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies pp.19, November 1996 (Retrieved 19 May 2009)

Name: Anonymous 2009-05-19 19:03

>>16
80 is ok. However, it's fucking pushing it. 76 gives you another indentation level before you hit the hard limit of 80. In decent and humane imperative languages (FIOC, JavaScript, See, Ruby) long lines are a code smell. Long lines are common in PHP as it is mostly coded by people who will happily shit on a floor, your floor.

There should be a punishment system for long lines that goes something like this:
1-72 Yeah! We rockin'!
72-76 Careful now. Maybe think about refactoring.
76-80 Oooh! You're pushing the limit there! you should definitely think about refactoring.
80-90 A stern warning should be issued to the miscreant.
90-100 A written reprimand should be issued. For a second offence employment should be terminated.
100-120 Removal of fingers. This ``person'' should not code again.
120+ Removal of penis. This ``animal'' should not be allowed to breed.

Name: Anonymous 2009-05-19 19:09

It is more important that code is readable, is maintainable, and works than that someone comes up with some cryptic fucking variable name. "Oh, of course db_con_hn is the database connection host string. Almost hit 80 characters there!"

wtf

Name: Anonymous 2009-05-19 19:19

>>18
I have my notepad++ set to display a line at 80 characters. But sometimes I just can't be bothered to add an additional line break, because I have a widescreen monitor so I can see nearly twice as much, and the code is far from finished so I don't care if it's aesthetically pleasing. I never went over 120 characters on a single line though.

Name: Anonymous 2009-05-19 19:24

>>19
If you can't keep line length below 80 characters without sacrificing readability you are doing it wrong or using an overlyVerboseAndShittyLanguage. db_conn is more readable than databaseConnection. If db_conn refers to something else than a database connection you are obviously dealing with PHP programmers and I advise you to have a mop handy to clean your floor!


for(int loopIndexCounter = 0; loopIndexCounter < 100; loopIndexCounter++)
    printf(">>19 is disproved by contrived counter example");

Name: Anonymous 2009-05-19 19:30

>>18
I agree with the spirit of this post. I cried myself to sleep when I found out that coding in Objective-C often mandates such long lines.

Name: Anonymous 2009-05-19 19:43

>>21
loopIndexCounter? Enterprise quality variable name.

Name: Anonymous 2009-05-19 19:45

>>21
My floor is carpeted, so I don't really need a mop...

Name: Anonymous 2009-05-19 19:46

CamelCase is the standard!!!

Underscores look silly and just add more characters. All lowercase in one word is even worse as it's usually unreadable.

Name: Anonymous 2009-05-19 20:37

>>25
JavaCase is not the standard.

Name: Anonymous 2009-05-19 22:51

>>25
Hyphens are superior.

Name: Anonymous 2009-05-20 0:49

I just try to use SINGLE words all the fucking time if I even need words. Also, 80 chars is standard. I break the limit if it's for something stupid that is better done all in one line because there is nothing to read, just spammed shit.

Name: Anonymous 2009-05-20 2:25

Even pulling out a handy trick in Sepples, I was barely able to keep this line under 80 characters.

typedef unordered_map<int, int> bjarne;
for (bjarne::iterator i = stroustrup.begin(); i != stroustrup.end(); ++i) {

}

In short: Fuck off. Your standards are antiquated. Get real editors and computers.

Name: Anonymous 2009-05-20 2:46

try a real language

Name: Anonymous 2009-05-20 3:18

My VT100 supports 132 characters per line.

Name: Anonymous 2009-05-20 3:33

>>29
You mean Sepples is incompatible with good style.

Name: Anonymous 2009-05-20 3:36

Also, 80 chars is standard.
For Hollerith punch cards.  Wow, 1970's acid flashback time, man!

>>29
typedef unordered_map<int, int> bjarne;
for (bjarne::iterator i = stroustrup.begin();
     i != stroustrup.end();
     ++i)
{
 // shit happens here
}

HTH, HAND

Name: Anonymous 2009-05-20 3:40

>>32
You might be surprised to learn this but it is not bad style to split long lines up in to multiple lines. In fact- that example is ironic in that good style would dictate he move the iterator declaration out of the loop, yet it is being given as reasoning why an eighty character limit is ``antiquated''.

Name: Anonymous 2009-05-20 7:21

Do me

$string=~s/[\x{fdd0}-\x{fdef}\x{fffe}\x{ffff}\x{1fffe}\x{1ffff}\x{2fffe}\x{2ffff}\x{3fffe}\x{3ffff}\x{4fffe}\x{4ffff}\x{5fffe}\x{5ffff}\x{6fffe}\x{6ffff}\x{7fffe}\x{7ffff}\x{8fffe}\x{8ffff}\x{9fffe}\x{9ffff}\x{afffe}\x{affff}\x{bfffe}\x{bffff}\x{cfffe}\x{cffff}\x{dfffe}\x{dffff}\x{efffe}\x{effff}\x{ffffe}\x{fffff}]//g;

Name: Anonymous 2009-05-20 8:11

>>34
move the iterator declaration out of the loop
And pollute a larger scope with the iterator variable? HIBT?

Name: Anonymous 2009-05-20 8:30

>>36
No, actually it is better to declare it before the loop, since it won't be redeclared every iteration.

Name: Anonymous 2009-05-20 8:39

>>28
if I even need words
I hate your kind so so much. You are what makes maintenance of old code so fucking difficult. Please never program for anyone other than yourself. Don't even add your code to open source projects.

>>37
What?!

I am definitely being trolled here. And it's working.

Name: Anonymous 2009-05-20 11:51

>>38
Declaring it outside the loop saves a constructor call if the copy constructor is declared explicit. Please refer to the C++ FAQ.

Name: Anonymous 2009-05-20 12:32

>>33
Happen to have one for people who don't like PIG DISGUSTING syntax such as the one you display?
Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List
All trademarks and copyrights on this site are owned by their respective parties. All comments and posts are the responsibility of their own posters.
- Tinychan + 2ch Mode -