I'd much prefer typing just letters vs letters and underscore, efficiency wise.
A few extra letters is pretty negligible to my efficiency/flow, underscore is a bit more jarring even if it isn't very much more of a deal and typing isn't the majority of what makes for efficient programming...
It still is like FUCK YOU, UNDERSCORE creeping into my brain.
Hah, why? Same naming convention for everything? I don't mind that so much. There's so much bigger fish to fry in the world of programming than naming things. =D
@TwitchTV, @Youtube: master-level zerg ladder/customs, commentary, and random miscellany.
The older I get the harder it is to remember everything under the sun. If I was still 14 I probably would just use whatever I felt like using at the moment.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
1. Follow the standard/style of the project you are currently in.
2. Follow the standard/style guide of the language you are writing in.
3. ?????
4. Do whatever the fuck you want.
One thing I do that probably annoys other people is to underscore private methods on a class. It means I can see at a glance which are public and it makes the auto complete on function call when you're writing the class that much quicker.
In other news AWS bill rose to $25 with no change to what I was doing. Now there's even more acronyms and mystery charges.
The one about the fucking space hairdresser and the cowboy. He's got a tinfoil pal and a pedal bin
I first have to stab myself since I work on projects that use double underscore for include guard names, no matter how many times we bring up that it is against C++ standards.
If you prefix anything with _underscore in a C++ project I will go :bowen: all over you.
single or double leading underscores are reserved for the compiler and standard library ( except for underscore followed by a number e.g. _1 )
alternative?
I think in C++ I might use casingSuchAsThis for member level variables of varying access level, and then CasingSuchAsThis() for public accessor methods
mightyjongyoSour CrrmEast Bay, CaliforniaRegistered Userregular
According to the google style guide, you should be using the underscore at the end, i.e. variablename_ . I don't think I agree with this though, personally I think I prefer a prefix to denote access level over postfix.
Posts
A few extra letters is pretty negligible to my efficiency/flow, underscore is a bit more jarring even if it isn't very much more of a deal and typing isn't the majority of what makes for efficient programming...
It still is like FUCK YOU, UNDERSCORE creeping into my brain.
Because being consistent is one of those things that is hard on what is likely code done by a lot of people on crunch/must work now time.
Hah, why? Same naming convention for everything? I don't mind that so much. There's so much bigger fish to fry in the world of programming than naming things. =D
C++, Java, Python, PHP, C#
The older I get the harder it is to remember everything under the sun. If I was still 14 I probably would just use whatever I felt like using at the moment.
1. Follow the standard/style of the project you are currently in.
2. Follow the standard/style guide of the language you are writing in.
3. ?????
4. Do whatever the fuck you want.
In other news AWS bill rose to $25 with no change to what I was doing. Now there's even more acronyms and mystery charges.
and I use meta for GUI variables that correspond directly to a named variable for binding
so "myObject.name" would bind to "lblName"
I have no clue.
The library itself (mostly) uses the stk prefix. But whenever it's referred to from another core library, it uses the stock prefix.
http://steamcommunity.com/id/pablocampy
single or double leading underscores are reserved for the compiler and standard library ( except for underscore followed by a number e.g. _1 )
*ducks*
I first have to stab myself since I work on projects that use double underscore for include guard names, no matter how many times we bring up that it is against C++ standards.
alternative?
I think in C++ I might use casingSuchAsThis for member level variables of varying access level, and then CasingSuchAsThis() for public accessor methods
This:
Is wrong.
Sounds right to me.
I find when most people want decimals, they almost never want floating point decimals.
I guess they call that radix independent floating point, I always just called it fixed point decimal.
Decimal is great when languages support it!
not sure something convenient to use exist, haven't looked to be honest.
looks like it has something for that.
At times it calls charts "tables" and it's really fucking confusing. It'll be like:
Why not call it a fucking chart? That's what it fucking is!
Go with "c" then. Once "chart" is passed in then there's nothing that needs to happen to it. You don't need to say "Chart chart" anywhere.
chart.getSeriesNames().get(0);
Makes a hell of a lot more sense than:
table.getSeriesNames().get(0);
Not sure if I hate you or love you.
Why do you do this to my emotions, man?
Yeah I wanted to avoid making bowen's blood boil.
Just because I'm having a really bad day.