Jane, I agree, I actually meant that I don't think there should be a discrepancy and that case-sensitivity should be the rule. As it is, apparently, as I found out today, I'd mistyped a file name with incorrect case, and java tried to run it as is, even though the case was wrong, but javac choked on its source, as it should. So go figure.

I couldn't figure out why I was getting so many weird errors until I saw that the class file I was trying to run, technically, didn't exist! lol! so then when I used the proper case, all was well.! So my bad, but still a flaw in the java usage in my opinion.

RE: java on Mac pissing you off; it seems it's doing that for a lot of peeps!… -Lots of complaints on the JDK 5 / JRE 5 and JRE 6 implementation for Leopard…

Smiles,

Cara  :)


On Sep 16, 2008, at 6:09 PM, Jane Lee wrote:

Apple is seriously pissing me off in regards to java support on OS X. I
wonder if it's a ploy to get everyone over to using cocoa+objc.
Anyway, in regards to java case sensitivity, there is more evidence (to me) that keeping case sensitivity would be more useful, the biggest and most obvious benefit being that it forces the code to be clean and readable and case lets the developer impart additional meaning and cut down on ambiguity without taking up more space. Plus most IDEs can handle this just fine in
languages where case sensitivity matters, e.g. intellij, eclipse and
netbeans for java.

cheers,
jane

On Tue, Sep 16, 2008 at 9:27 AM, Cara Quinn <Cara- [EMAIL PROTECTED]>wrote:

Okay, my bad, pilot error!  lol!

Very sorry for the inconvenience. It turned out to be partially a weird issue of difference in capitalization (of all things) between the usage of
javac and java, that really shouldn't be there in my opinion.

Have a great day, and catch y'all laters!…

Smiles,

Cara  :)


On Sep 16, 2008, at 8:58 AM, Cara Quinn wrote:

 I know All, a little late on the uptake!  lol!  But I just started
developing again with Java on the Mac, or at least am trying to, and I've
run, immediately, into an obnoxious prob.

The last Java update, a few months ago, which shouldn't have impacted the current Java 5 installation on Leopard, seems to have broken my standard
JDK.

I can't even compile basic java apps, as the java.lang library isn't
recognized. So a path somewhere has been changed, without my knowledge.

What's the deal?…  Has anyone else run into this, and where should I
start looking on the system?…

I'd had trouble locating the actual folder for the java.lang lib before, as I recall, so now it's become an issue, as I really do need to find it as
opposed to simply wanting to know where it might be.  <smile>

anyway, any help anyone might send along would be great! -Scott, ya out
there?…  <smile>

Have a great day, All, and thanks for reading!…

Smiles,

Cara  :)


---
View my Online Portfolio at:
http://www.onemodelplace.com/CaraQuinn



---
View my Online Portfolio at:
http://www.onemodelplace.com/CaraQuinn




---
View my Online Portfolio at:
http://www.onemodelplace.com/CaraQuinn


Reply via email to