> Actually, immutability is complicated. Absolutely, and to be honest, for a static analysis tool, the java.io.File doesn't seem all that bad. At least compared to accurately detecting benign data races, such as with String's hashCode() method. In regards to j.i.File, I see it as a case of 'as soon as you interact with anything native or abstract, all bets are off'. But there is a limit to the usefulness of immutability, where the real benefits comes with knowing operations are side-effect free.
Still, I think there's decent possibilities for @Immutable in regards to static analysis tools. Regards, Graham PS. if anyone knows any interesting resources regarding static analysis and benign data races, I'd be delighted to hear about them. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
