scott wrote:
>> How to translate from the concept in your mind to a working program.
> 
> I didn't get the impression that is what Andy was complaining about, 
> after all he says he can program in Java, so converting from concept to 
> C shouldn't be very different from converting from concept to Java.

You know what? In Java, if you reference a null pointer, a little 
message pops up that says "hey, you just dereferenced a null pointer". 
And it even tells you where it happened. In C, your program just behaves 
bizarely.

Ditto for EOF, array index out of bounds, out of memory...

Java has a seperate Boolean type, so you can tell when a function 
returns a numer and when it returns a Boolean. (And you don't have to 
memorise whether 0 is true or false. And if you accidentally try to use 
a number where a Boolean is expected, the compiler *tells* you about 
this. And...)

Memory leaks? What memory leaks? No dangling pointers here either.

Need I go on?

In short, Java is a suck-ass language, but at least it's easier than C.

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message