Case sensitivity can be a pain in some aspects, but I shudder to think of what I have seen and no doubt will see more of in case insensitive languages and lazy partners and other developers. grin. There is a case for case preservation, but no matter what, naming conventions can come in handy. as well as IDEs that can do these for you so you don't have to think as much hehe.
Anyway, Java is tied to the OS (in a way, i.e. 1.3 is unavailable on Leopard while 5 is tiger and leopard only, etc.) which was the reason for all the outrage when a final non-nda non-developer-beta Java 6 wasn't officially included with Leopard, Apple doesn't seem interested in getting java 6 on non-64 bit intel, apple isn't entirely in sync with the rest of the releases. how could a developer not get at least sort of irritated? Now, I would be in heaven if Apple decided to contribute to the OpenJDK bsd port. All I've seen from them however is only a willingness to improve aqua l&f in their in-house java 5 and pretty much no comment on when or if they'll ever do anything about java 6 or 7. I haven't done much with java as of late (iPhone and Mac is getting all my love), but when I'm doing any classwork or actual paid work having to do with it, I do a lot of it in windows in vmware and not on my Mac. It just makes my life easier. I bet I wouldn't be the only one doing so on a Mac either, unfortunately. Apple used to really care about Java development, and now it seems to be virtually ignored nowadays. cheers, jane On Tue, Sep 16, 2008 at 10:39 PM, Cara Quinn <[EMAIL PROTECTED]>wrote: > 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 :)
