[Skipperdoo32]

PLEASE HELP.

I JUST started with all... this. Never tried programming before (except for a short experience with Textpad at school, one time).

I read through Frooxius's thread on "What is a CPU". What is the next step? I feel more enlightened, for sure, but when I try to read the other articles and tutorials, I get so unbelievably lost!

My main focus right now is learning HOW to program. For example, where do I enter in these "opcodes", and where can I learn them? Is there any kind of software of some sort that I need to download?

Help! Please!

---

And what does "C++" mean?

[Skipperdoo32]

PLEASE HELP.

I JUST started with all... this. Never tried programming before (except for a short experience with Textpad at school, one time).

I read through Frooxius's thread on "What is a CPU". What is the next step? I feel more enlightened, for sure, but when I try to read the other articles and tutorials, I get so unbelievably lost!

My main focus right now is learning HOW to program. For example, where do I enter in these "opcodes", and where can I learn them? Is there any kind of software of some sort that I need to download?

Help! Please!

---

And what does "C++" mean?

[Skipperdoo32]

And PLEASE don't just say "Google it", because I've been trying that for the past few hours now, and I am still so lost...

[Skipperdoo32]

But how is all of this entered in? (I probably sound like a fool, since I don't know what I'm talking about, entirely) but where does the programmer enter in these opcodes?

---

Oh wait! Nevermind. Just found my answer:

http://www.hackcommunity.com/Thread-C-C-...-languages

[Skipperdoo32]

Wow...!

Exactly what I was looking for. Thank you very much for your help!

Once I understand programming, I'll give those hacking tutorials another go.

[Frooxius]

If you're new to programming, I don't recommend starting with assembly programming, since it's more difficult and confusing for beginners, even for many intermediate programmers. Also, if you were to program in assembly, you wouldn't be writing opcodes themselves either - instead you would use the assembly programming language and write names of the opcodes - mnemonics. Then a tool called assembler would convert these names to opcodes for you. It would be extremely tedious to write programs like this.

I recommend starting with a high level programming language, which allows you to write the program in much easier manner. As my article you read explains, the opcodes (instructions) are generated for you by the compiler, so you don't have to care about them at all, which makes everything much simpler.

I don't recommend starting with C/C++ either. There are several languages that might be good for beginners, for example Python, Pascal or VB.NET seems popular here too because of its simplicity. For these, you can find various development tools - you download a program, where you can write your code, then compile and run it.

The 7th Sage: Well you can break code into parts even in C, OOP just makes the task more easier, better manageable and more powerful, but it's not like you can't do it with C too, it's just more tedious.
And by security, I guess you mean that it's less bug prone? I mean... it can be a bit confusing when you just say security, because it might be interpreted that the code is more secure against attacks, which it might somewhat be because of better management, but it's not that much and a bit indirect.

[Frooxius]

Sorry, it just sounded something like that and I wanted to clarify things a bit for Skipperdoo32.
Yeah, access specifiers are means of encapsulation, one of main principles of OOP. Though even the others like polymorphism and inheritance can increase the security when programing by allowing easier code management and decreasing chance of making a mistake that can result in problems and run-time bugs (or compile time).