B
bbawa1
What does the term immutable mean? Could you please explain me with
examples.
examples.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
Jon Paal [MSMD]
A
Alex Meleta
Hi,
.... immutable object is an object whose state cannot be modified after it
is created. This is in contrast to a mutable object, which can be modified
after it is created....
The source (and examples): http://en.wikipedia.org/wiki/Immutable_object
Alex
http://devkids.blogspot.com
.... immutable object is an object whose state cannot be modified after it
is created. This is in contrast to a mutable object, which can be modified
after it is created....
The source (and examples): http://en.wikipedia.org/wiki/Immutable_object
Alex
http://devkids.blogspot.com
R
Richard Clafton
Hello (e-mail address removed),
Google is your friend when looking for definitions....
Enter into google:
define:immutable object
What does the term immutable mean? Could you please explain me with
examples.
Google is your friend when looking for definitions....
Enter into google:
define:immutable object
T
tomk148
"LOLRTFM"
immutable objects are significant because of how the compiler will
deal with them. for instance C# strings are immutable, so if you say
string s = "bl";
foreach (int i=0; i<10; i++)
s += "a";
s+= "h";
the end result is what you think it would be, but the compiler will be
creating lots more temporary strings in between.
"bla", "blaa", "blaaa" ... etc
if strings weren't immutable you wouldn't have as many temporary
objects, but things maintenance behind the scenes would be slower.
When objects are immutable the compiler has more assumptions to work
on and will be faster in the long run (assuming you avoid stuff like
the above). So if something is immutable you should be aware of
temporary object creation getting out of hand.
immutable objects are significant because of how the compiler will
deal with them. for instance C# strings are immutable, so if you say
string s = "bl";
foreach (int i=0; i<10; i++)
s += "a";
s+= "h";
the end result is what you think it would be, but the compiler will be
creating lots more temporary strings in between.
"bla", "blaa", "blaaa" ... etc
if strings weren't immutable you wouldn't have as many temporary
objects, but things maintenance behind the scenes would be slower.
When objects are immutable the compiler has more assumptions to work
on and will be faster in the long run (assuming you avoid stuff like
the above). So if something is immutable you should be aware of
temporary object creation getting out of hand.