You know what? this is the absolute worst community i have ever seenInteresting to draw conclusions about the whole community from a single answer. If you knew the single members a little bit better, you would not take everything so seriously.
Since we're all in peace again, let's discuss switching from javaStyleNamingConvention to hacker_cpp_convention. I'm sure Laurent is very open-minded in that regard! ;)Is there even a library apart from Boost that uses the standard_style convention? :P
Is there even a library apart from Boost that uses the standard_style convention? :PYes! FWMS, FWCS, FWU and FWSG - yeah all FlexWorld libraries. ;D
Yes! FWMS, FWCS, FWU and FWSG - yeah all FlexWorld libraries.Don't forget the upcoming FWB (FW Build) and FWL (FW Language). :P
and thank you very much i did google with why did sfml 2.0 go to camel case and got no results.When I google why did sfml 2.0 go to camel case, there are 131k results, and the "New naming convention" thread is the sixth (or third) result of the first page, I wouldn't call that "no results". ???
Since we're all in peace again, let's discuss switching from javaStyleNamingConvention to hacker_cpp_convention. I'm sure Laurent is very open-minded in that regard! ;)To make it interesting I think You, Nexus and Laurent should take turns using all three in a way so that every lib has different convention than the other two. To make it even better replace hacker_cpp with something else to not be consistent with STL either. :D
You use hacker_cpp_convention?? Seriously? ???QuoteYes! FWMS, FWCS, FWU and FWSG - yeah all FlexWorld libraries.Don't forget the upcoming FWB (FW Build) and FWL (FW Language). :P
so that every lib has different convention than the other twoToo late, Nexus already got weak and changed to helloJava. SFGUI is still at OldSchool, so it's already different. ;)
You use hacker_cpp_convention?? Seriously?Yep.
what_the_hell("?!?!?");QuoteYou use hacker_cpp_convention?? Seriously?Yep.
Is there even a library apart from Boost that uses the standard_style convention? :PI was telling that someone just the other day. And now Tank comes out with his hello_stefan_convetion.. :(
what_the_hell("?!?!?");[...]And now Tank comes out with his hello_stefan_convetionI assume you don't like it? I even don't get why people use different styles for C++. In other languages people tend to stick to the naming conventions the standard lib uses, at least in Python, JavaScript, Ruby and similar languages.
Too late, Nexus already got weak and changed to helloJavaHey, while you were saying "good that you did it", I fought the camelCase convention (http://en.sfml-dev.org/forums/index.php?topic=6709.msg44956#msg44956)! :D
I even don't get why people use different styles for C++.Because the default_one seems to be awful enough that almost nobody likes it. Probably because people consider all the underscores less readable, especially in combination with operators.
Hey, while you were saying "good that you did it", I fought the camelCase convention!That's one point for you -- however the "good that you did it" was targeted at the "I change the naming convention", not the camelCase. ;)
Because the default_one seems to be awful enough that almost nobody likes it. Probably because people consider all the underscores less readable, especially in combination with operators.Strange, because underscores are easier on the eyes than helloJavaWorld (compare with hello_java_world, I can better separate the words). But well, in the end it's just personal taste.
Strange, because underscores are easier on the eyes than helloJavaWorld (compare with hello_java_world, I can better separate the words).By separating the words inside identifiers more easily, you make separating the identifiers themselves harder. In other words, it's more important to see the space between identifiers rather than the space inside them. By using underscores, which look like spaces, the limit between words-inside-identifiers and identifiers themselves gets thiner, which makes the code harder to decode.
Which one is the easiest to read?Honestly? The first one, both for book- and source reading. And if something's good readable in a book, then it should be great in source too. Or do you want to tell me that you don't want to read source code like a book? ;)
Don't worry, I use the superior_cpp_naming_convention when I code in Java or JS in retaliation.Quotewhat_the_hell("?!?!?");[...]And now Tank comes out with his hello_stefan_convetionI assume you don't like it? I even don't get why people use different styles for C++. In other languages people tend to stick to the naming conventions the standard lib uses, at least in Python, JavaScript, Ruby and similar languages.
I assume you don't like it?I just didn't ever see anyone use hello_stefan while not joking or messing around except boost(glorified std) and std(if they changed it, they'd break so much code it's not even funny).
I even don't get why people use different styles for C++.Because c++ doesn't make programer brainless? ;D
As long as it's not hElLoWoRlD(), but I haven't seen that so far.This would make great april fools joke from Laurent.