lukatmyshu
Senior member
The exception is thrown to the command line because the programmer did something silly ... namely he didn't put an intelligent error message. The thing is, java tries REALLY hard to make you be good and realize when things are failed. Half of the reason it's slow is because of it's exception handling routines, which are implemented as table lookups and long-jumps. But they are there so that people won't have to see FIleNotFoundException. It actually takes WORK to ignore these messages.
Secondly, C++ is a sucks-ass language because it is too powerful. There are things we don't have to do anymore. Ninety percent of the time .... we don't need to do pointer-arithmetic. And if we couldn't .... we wouldn't get a LOT of the security-problems we have now (buffer-overflow errors which allow arbitrary bits of code to be executed are an exploit that is directly related to this problem). Multiple inheritance is a very confusing thing (basically if you inherit from two objects that have the same method .... which one do you inherit from?). All these issues were well thought out and java offers a very strong and precise OO implementation.
And to the Sys-Admin who wants it to be like "java ./foo.class" <---what the hell is that suppposed to mean?
You are not running "java" with a file .... you are passing the name of a class that has a main-method to be executed. It's a completely different concept and makes sense if you know what is actually going on.
Secondly, C++ is a sucks-ass language because it is too powerful. There are things we don't have to do anymore. Ninety percent of the time .... we don't need to do pointer-arithmetic. And if we couldn't .... we wouldn't get a LOT of the security-problems we have now (buffer-overflow errors which allow arbitrary bits of code to be executed are an exploit that is directly related to this problem). Multiple inheritance is a very confusing thing (basically if you inherit from two objects that have the same method .... which one do you inherit from?). All these issues were well thought out and java offers a very strong and precise OO implementation.
And to the Sys-Admin who wants it to be like "java ./foo.class" <---what the hell is that suppposed to mean?
You are not running "java" with a file .... you are passing the name of a class that has a main-method to be executed. It's a completely different concept and makes sense if you know what is actually going on.
