Jump to content

  • Log In with Google      Sign In   
  • Create Account

How long would it take to...


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
22 replies to this topic

#21 James Miller   Members   -  Reputation: 166

Like
0Likes
Like

Posted 01 February 2013 - 11:24 PM

I've been trying to follow tutorials for a good week now, but I'm finding myself frustrated at the fact that, when someone provides a tutorial code and basically says "just throw this in your compiler and run it", it can't just be entered into any C++ compiler. I'm finding myself lost with the fact that one has to go and, (if I've got this right), hunt down random libraries, headers etc, or compile their own. I guess that's one thing that programming in the QBASIC environment never taught me, and is one of my shortfalls in making the jump to C++. You could take code from anywhere and slap it in, compile it and run it, but as far as C++ goes, I feel like I'm going way too slow. When I was doing my games programming diploma at TAFE, they never even bothered to cover anything past making a simple real time strategy in C, never taught us how to make headers, or utilize custom libraries.

At the moment for example, I'm following Lode V's Raycasting tutorial -> http://lodev.org/cgtutor/raycasting.html and Codeblocks with the GNU C++ compiler. I would love to know what I need to be able to do to take the code he's provided and compile it successfully, have it spit out a .EXE I can run.

However, I'm finding that even after popping the appropriate libraries into their respective directories, (the SDL referred to in his tutorials) I'm running into compiler-killing errors. So I guess my next question is, given that there's no striaghtforward tutorial to setting up up library X with compiler Z, what would you guys recommend I use? Should I abandon codeblocks for another compiler and set of libraries that seem to be the standard? Every tutorial I find seems to always branch off into different directions and this is the one thing that tended to lose me; some will say to use Visual Studio, others will say use DevC++, etc, but often the codes don't seem to be interchangeable.

 

I would search before posting again, but I'm not quite sure what terms one would search for in regards to my question, but then again, I'm posting because I'm really keen, I really do want to learn, and I don't care how long it takes. I've spent the last week also touching up and studying maths furiously, have torn through a considerable amount of Khan Academy videos and begun quizzing myself, and making simple C++ programs to try and push what I've learnt as I guess this would be a good way to learn, by experimenting.

I know my posts are dead long, but anyone who has the time to respond, it would be mega appreciated, and when the day comes that I become an evil Russian billionaire, I'll happily pay the favor back however you like.


Edited by James Miller, 02 February 2013 - 12:34 AM.


Sponsor:

#22 swiftcoder   Senior Moderators   -  Reputation: 10444

Like
0Likes
Like

Posted 02 February 2013 - 10:59 AM

I've been trying to follow tutorials for a good week now, but I'm finding myself frustrated at the fact that, when someone provides a tutorial code and basically says "just throw this in your compiler and run it", it can't just be entered into any C++ compiler. I'm finding myself lost with the fact that one has to go and, (if I've got this right), hunt down random libraries, headers etc, or compile their own. I guess that's one thing that programming in the QBASIC environment never taught me, and is one of my shortfalls in making the jump to C++. You could take code from anywhere and slap it in, compile it and run it, but as far as C++ goes, I feel like I'm going way too slow.

<somewhat offtopic>

This is one of the many, many reasons that we don't recommend C++ as an early language. The number of pitfalls is ridiculous - a language like C#, Java or Python insulates you from most of this type of concern.

</somewhat offtopic>

 

More relevantly, perhaps: start small. Work your way up from "Hello, World!", learning all the basics along the way - source/header files, makefiles, static versus dynamic linking. C++ isn't the language to use if you want to go off half-baked.


Tristam MacDonald - Software Engineer @Amazon - [swiftcoding]


#23 James Miller   Members   -  Reputation: 166

Like
0Likes
Like

Posted 02 February 2013 - 12:34 PM

I've been trying to follow tutorials for a good week now, but I'm finding myself frustrated at the fact that, when someone provides a tutorial code and basically says "just throw this in your compiler and run it", it can't just be entered into any C++ compiler. I'm finding myself lost with the fact that one has to go and, (if I've got this right), hunt down random libraries, headers etc, or compile their own. I guess that's one thing that programming in the QBASIC environment never taught me, and is one of my shortfalls in making the jump to C++. You could take code from anywhere and slap it in, compile it and run it, but as far as C++ goes, I feel like I'm going way too slow.

<somewhat offtopic>

This is one of the many, many reasons that we don't recommend C++ as an early language. The number of pitfalls is ridiculous - a language like C#, Java or Python insulates you from most of this type of concern.

</somewhat offtopic>

 

More relevantly, perhaps: start small. Work your way up from "Hello, World!", learning all the basics along the way - source/header files, makefiles, static versus dynamic linking. C++ isn't the language to use if you want to go off half-baked.

 

Well, I've been reading through a book (C++ For Dummies. I also have Accelerated C++ and C++ The Complete Reference for later), although I'm learning how to code without any major issues, it's a matter of compiler compliance. (ie the tutorials in my book, oddly enough, use printf instead of cout, despite being a c++ book). Problem is, if I try tutorials online, I end up on the same problem; tutorials written by a group of different people, with vague areas such as "oh if you need this header, just make one yourself" etc. You need to already be able to professionally code, in order to learn to code it seems.

What I would love is to be able to pay for a digital tutor of sorts, someone I could ask questions to etc. The downfalls of tutorials are that they sadly, do not talk back whereas a tutor would be infinitely useful, especially one who has been involved in some form of either games programming or game engine programming (I'm curious and keen to try out both at some point). I've done Java and C in college, but it didn't really help me learn about how to tackle C++, especially game-related aspects, then again, my games development teacher consisted of a guy whos only programming experience consisted of a DOS style interface for a bank that he built.

 

I will take myself back a few steps though, I'm going to give myself at least 3 years max to try and get a basic Raycaster out there. If 7 year old youtube kiddies with ADD can do it, I don't see why I shouldn't be able to. I'll look up some tutorials on headers, makefiles, and linking, as it sounds like the kind of thing that has me a bit stumped at the moment. Thanks for your response by the way!






Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS