I think titles are almost completely meaningless in this industry. You can choose to distiguish between different titles, but since there are no widely used standards, those titles won't convey any information outside your purview.There are plenty of people with the title Software Engineer who stuggle to write a simple batch file or script and...

Ah ha. The problem is that you've confused path and classpath. The path is where the OS looks for executable programs (incidentally, class files can be configured as such, but that is another topic), whereas the classpath is where the JVM looks for class files. They are completely separate and different. You don't want that packtest stuff in...

Looks like classpath isn't set.Try using the set command instead, "set c" should show all variables starting with 'c'.

It's not necessary to build a jar file, to use packages. (You may want to build one for deployment, however, but that is another subject).Simply this should do the trick:set classpath=%classpath%;c:\packtestpushd c:\packtestmove utilities\TicScreener.java com\utiljavac com\util\TicScreener.javapushd objectsjavac Owner.javajava OwnerPart of your...

> Gosling's comment is what I think we should use as a> benchmark when judging a programming language: How long it> takes to create something robust with a given language.> Since most programming languages are Turing-complete, you> can pretty much use any language to write any program you> wish. I used to think that I was productive with a>...

> Its embarrassing that the interviewers/tech editors did not catch this.Probably wasn't in the throws clause.

> Some people have said that checked exceptions are an> attempt to make java idiot-proof, a sort of dumbing-down> approach to protect programmers from themselves. To me,> that focuses on the wrong side of the equation. The goal> of checked exceptions is not to make *using* an interface> easier, it is to enable programmers to *design* more>...

> As an "Intellectual" it is important that you seperate> logic and emotion.She called herself an "engineer" not an "intellectual" -- there is little overlap between the two (especially after the title inflation of the dot com boom!). Anyway, logic shouldn't and cannot always be separated from emotion. Nevertheless...Sue, do you apply these...

Smart-ass quips aside, I think I agree with Brandon on this. Java doesn't need more exception cruft, it needs less. My guess is that Sun wanted Java to have mass appeal, which means it needed to try to be idiot-proof (at least a lot more so than C and C++). Hence, checked exceptions, with the thinking that API developers could force proper...

> How about having "unexpects" keyword ?It is already there, but it's called "//unexpects". ;-)

> Rather than> discarding it altogther, perhaps there's some way to> encourage users to use it properly?What is the "proper usage" then? I think that Anders might have been saying that a big problem with the Java implementation is that there is no good proper usage.

Oops -- I got timed-out, so my preview was posted before I had a chance to correct "acceptible" to "acceptable."

> Sure you could write a method using the wrapper methods> you listed as long as you are use try/catch blocks to> catch the NumberFormatExceptions that will be thrown.That was exactly what I meant by "try" (I made it bold, but that probably wasn't explicit enough, since in both cases it was next to other text that was bold).> The issue really...

Hmm. Couldn't you just try Integer.parseInt(), then try Double.parseDouble() (or Float.parseFloat(), if you like) and leave all else as String?

In conjunction with this, you could write a simple script that goes through all the java files in your project and modifies the line matching something like "^\s*public static final boolean DEBUG = (false|true);\s*$" (I'm not a regualar expression guru, so it can probably be improved upon) to either true or false as appropriate (debug vs...