in reply to Re^10: The fallacy of the *requirement* for read-only instance variables.
in thread The fallacy of the *requirement* for read-only instance variables.
Oh really? I find it very practical that my number literals are immutable.
In Java strings are immutable, but you can still assing a new String to a String-typed variable. Perl follows the exact same model for numbers. Why is this suddenly meaningless, but not in the Java case? You might say because you can think of mutable strings but not of mutable numbers, but that's just a limit of your imagination.
Also declaring something that contradicts your line of thought as "meaningless" without any explanation isn't very good style of discussion.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^12: The fallacy of the *requirement* for read-only instance variables.
by BrowserUk (Patriarch) on Apr 18, 2011 at 12:44 UTC |