http://www.computer-books.us/

Just found this on digg.com.  There's a couple of Java books for
download there.

As for the switch from C to Java, you mainly need to wrap around the
Object-Oriented idea.  C++ covers this in great detail (I went pretty
seamlessly from C++ to Java, just because SO many of the principles are
the same).  I don't think they really make a book specifically for Java
for C programmers, but most should be able to give you the OOP
introduction, and from there you should start to pick it up pretty
well.

Also, another great tool is the Java API.
http://java.sun.com/j2se/1.3/docs/api/.  I know, it's a lot to digest
now, but once you start getting into the language, that will explain
EVERYTHING you'd need to know about certain objects.

Happy hunting!

I can't recommend a book on Java for C programmers but I'm pretty sure there
are some. I'm sure I've seen this question asked and answered on this
newsgroup before. Try doing a Google Groups search of
comp.lang.java.programmer and search for 'C' and 'Java' (and maybe 'learn')
and you should find several recommendations.

--
Rhino

I'd recommend Hardcore Java (O'Reilly).  I could not get through
Learning Java because I knew how to program and it was too slow.
Hardcore Java teaches you advanced techniques and concepts and I was
able to pick up on syntax along the way.

I've tried both conversion books and beginner books for learning new
languages, and I find beginner books MUCH more effective.

It's a matter of mental mindset. Every language corresponds to a model
of how programs work. Someone who is comfortable with a language's model
is much more likely to produce smooth, effective code in that language
than someone who is thinking in the model from a different language.

The more I make myself ignore all the other languages I know, and focus
on the language I'm learning, the better I do at getting my brain
wrapped around the right model.

The "programming in X for those who know Y" books tend to keep me
thinking in language Y's model, rather than getting me into language X's
model.

This is perhaps most important of all for the C to Java transition. A
lot of Java syntax looks superficially like C, but the model of what is
going on underneath is profoundly different.

Patricia

see http://mindprod.com/jgloss/cpp.html
for some recommendations.

I learned C++ first.  I got in SO much trouble imagining that Java
worked the same as C++ just because the syntax looked familiar.

Such "C to Java" (or similar) guides can be pretty useful. But an
important step, as others have pointed out, is getting sufficiently used
to a new language such that you're not thinking of it in terms of
another more familiar language you already know. Getting to know a new
language in direct, first principle terms is pretty essential if you're
going to do any significant amount of work on it. As an example of what
may otherwise happen: you sometimes see programmers going out of their
way to make a new language look like, and behave like, a language that
is more familiar to them. Bully for them, perhaps, but as soon as other
developers come along, more proficient in the language in question, they
will look at the Frankenstein code and see a confusing mess.

I would recommend attempting to do a small project in Java.  Like you, I
started with C.  It was easy to pick up Java's syntax and grammer, but
the elegance was only realized as I started extending objects, creating
and using interfaces, abstract classes, exceptions, etc.  I noticed that
Java allows me to spend more time in design whereas C requires more time
coding (leaving less time for design.)  In the beginning, inevitably,
you will write some Java code in C-style.  But as you get to know the
language you will go back and realize what you could have done better.
Dive in!  I found that C made me better Java coder and that Java made me
a better C coder.

Good luck!

A quick find didn't show the mention of "head" in this thread so...

Head First Java : Your Brain on Java - A Learner's Guide

This book is great. Read the reviews on amazon. People like this. So
did I. It makes Java jargon make sense quickly.

Peter

A quick find didn't show the mention of "head" in this thread so...

Head First Java : Your Brain on Java - A Learner's Guide

This book is great. Read the reviews on amazon. People like this. So
did I. It makes Java jargon make sense quickly.

Peter