It will be extremely beneficial to learn C (not necessarily C++), because you'll begin to understand how the JVM is written and why it works the way it does. You get to learn in much greater depth about how the whole end-to-end process of making the machine do things works - memory bandwidth, cache pollution, etc.

There are places where C and C++ still rule and it's always good to know you can get down and dirty with it if you have to.

You will only fight with pointers if you have a bad design.I've never had to fight with pointers, in fact pointers made it easier for me to get things done.

Pointers are only a problem in a bad design.

Anyway, my computer graphics class uses C to work with OGL. There are reasons as to why they do this. I don't know what they are though but I believe it has something to do with C still being important.

It looks like C might actually be helpful. I could even use eclipse for development with some plugins, which is a big plus. Theres also plenty of code written in C which is a good reason to learn it. Is there a place I can learn all about the language syntax and standard library? what about "The C Programming Language" don't they call this K&R? Thanks again for the help! I hope that's not too many questions..

I was wondering if there is any good reason to learn c or c++ once you know java pretty well. Are there any benefits at all or is it a waste of time?

Usually it's a complete waste of time.Except in case your boss absolutely needs you to use it.

The usual way of many long time programmers has been: assembler, C (1), C++ (2), then a real OO high-level language like Java or nowadays the Java clone C# (from the Delphi guy) + NET. Some of course started with Cobol and will end with it. :-)Usually it's not neccessary to go the way backwards however.

In case you want to spend your limited time on applications and games, not low-level tools/drivers/etc, there's no need to learn assembler or its C wrappers.

(1) which is a macro assembler.(2) which is an object orientated macro assember. Because most C fans started to use C++ one day, they continued to write C programs in C++.

It will be extremely beneficial to learn C (not necessarily C++), because you'll begin to understand how the JVM is written and why it works the way it does. You get to learn in much greater depth about how the whole end-to-end process of making the machine do things works - memory bandwidth, cache pollution, etc.

Don't you say. It's actually unimportant to learn C++ to understant how compilers work. The real important thing, to learn how CPU works, is hard to do from C, it's MUCH more direct and easy from assembly. Some programmers were able to get a clue from drawing of CPU, the others from some nasty tests and hard 20 hours of programming.

Of course there are numerous articles, and arstechnica.com.

Optimalization of cache by C++ programmer could be called an reordering and additing few compile switches by an optimist. (Remember a fire of an optimist from Terry Pratchet book? Two wood pieces and a disapearing smoke.)

BTW a some test C++ knowledge. You have on your computer a few compiled .obj files (COFF), you know names of methods that needs to be exported in a library, you know name of library. You have cl.exe, and link.exe. You can't receive any other manual, programs, or anything. Your CEO was pissed locked the door, computer isn't connected to any network for security reasons, and you need to create a windoze dll file until he returns. And of course you can't recompile source files.

If you REALLY know C, you should find a solution, otherwise you are slave of an IDE.

message1db"This is message of a really simple ASM program",0message2db"name of window",0message3db"This program would terminate, if you will see an error window don t be lazy and append call to ExitProcess,0 to the end of the program",0

.code

fromthisline:

invokeMessageBoxA0, addrmessage1, addrmessage2, 0

invokeMessageBoxA0, addrmessage3, addrmessage2, 0moveax, 0

endfromthisline

It might work, I didn't tested it. It would give a feeling of a "low" level language.

Sure, ANSI C is well documented, but APIs things like GTK -- yuk! The Javadocs are wonderful -- and they have the lovely "@since" and "@deprecated" tags!

Will.

Too bad that people still make documentation like if they were programming in C. Just document 50% of it and let people guess the rest. Sometimes i even see apis with generated javadoc dcumentation almost made of empty tags.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org