On Sun, May 25, 2008 at 9:57 AM, David Leangen <[EMAIL PROTECTED]> wrote:
> The point is that unless you can _guarantee_ that parameters are immutable, > then a lot of damage and bad side effects can happen during a method call. And "final" does NOT protect anything within the method call (seen from the outside). For primitive types and object references, they are already safe. And for mutable objects (incl arrays), final doesn't prevent any changes. It only matters for within a method, or block for local variables. Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
