c++

starting to learn programming with C++; this shit is a bitch. i've been wanting to learn, so i can begin to develop a game using the source engine, but damn, any tips?

- learn how pointers work
- learn what manual memory management means
- learn how RAII works
- smart pointers are your friend
- STL is your friend
- allocate most shit from stack, not from heap (ie. avoid using new and delete) -> safer code and better performance
- remember: C++ sucks but it still beats C#, Java, Obj-C, C, and such crap languages

C++ can become insanely complex, but well, it actually is insanely complex. My advice would probably be to find a free software game written in C++ and take your time to study how that game works. Get yourself a C++ reference manual, I didn't bother trying to study C++ syntax but just reference the manual whenever unfamiliar syntax pops up in the code I was studying.

>>2
When you explain a language to a beginner as a jump start, all of the language's failures become immediately obvious.

>>2
IHNBT. But also,
C# > Obj-C > Java > C++ > A steaming pile of dog urine in the snow
C is incomparable.

>>2
Better than C

muahahahaha

>>6
muahahahaha
Back to Reddit News, ``please''.

>>7
no!

muahahahahaa

>>2
I refuse to be trolled _{(and I know that you are a troll because your post is so braindamaged that it cannot be written by a honest human)}.

You should stop teaching C++ and start learning some ethics.

you'd have better started learning with c

>>9
Explain what is braindamaged in >>2

>>12
YHBT

if you want to become proficient in sepples:
learn c++11 lambdas, auto
learn the type system
learn const
learn pointers and references
learn some design patterns and design techniques
learn what the standard library makes available to you and what things in the standard library you should never use.

ok now you're doing alright. there's more!

understand what the standard guarantees and what it doesn't. if you end up using compiler specific extensions or behavior then make sure you know you're relying on that and it's documented in your code. you should probably also use a static_assert to make the code fail to compile when using a different compiler if you're relying on unique behavior.

learn the rest of the c++11 stuff you didn't figure out like move semantics, rvalue references, constexpr
learn the stl algorithm header
understand templates; how they can be used to do good things and horrible things

and i probably forgot tons of stuff to say because sepples is overfuckingcomplicated and retarded.
the C++ FAQ on parashit ( http://www.parashift.com/c++-faq/ ) is somewhat helpful.

>>14
You forgot that C++ is completely fucking useless without Boost, QT, or some other decent library of this sort.  Standard C++ library is mostly a joke, a crippled one even.

>>15
C++ without Boost is actually less useful than C for small and mid-sized projects.

You don't have to be using Boost. Don't.

yain't red da standard

>>16
As opposed to C++ with boost which is less useful than C for all sized projects.

ITT: retards that don't understand the greatness of SEPPLES

>>20
An individual that doesn't understand SEEPLES

>>1
I programed many games with C++ on my job.
I'll tell you how to learn it.

1. Read a basic reference for C++.
2. Read samples written in C++/DirectX.
   Direct3D, DirectSound, Direct*** and stuff.
3. Take a cup of coffee.
4. Shutdown your PC, and don't think about programming twice. NEVER!

>>19
Yeah, that's why they had incorporated a fucking half of Boost into the new standard almost verbatim.  Not that it means that any of these things is of any use to a mentally sound person.

Anyway if C89 were Perl, C++03 would be PHP4.  And C++11 would be PHP5.

don't use sepples. i once red the whole stroustrup book. true story.

a shit

C++ is crap, but at least it's better than C for when you're forced to use something FAST AND SCALABLE.

It's better than C because it has EXCEPTIONS and thousands of other great high-level language features that really fucking belong in the high-level language area while still forcing you to carefully discern . and -> and be very mindful about where it stores your bits and which entity is responsible for their deallocation.  It feels like being a CTO in a large technological company and in addition to your primary tasks like architecture or strategic planning having to micromanage every single employee to stop them from eating glue.

And if you forget to add const or * in one single place in your code g++ will spam you with at least 10kb of indecipherable error messages, and at most, well, I don't know, my personal record is 763 kilobytes of error messages because of a single forgotten token.

>>27
Learning is fun!
http://technet.microsoft.com/en-us/library/cc767887.aspx

GDB the GNU Debugger B