comment on

This (Stop creating mutable objects.)

Imagine:

If your bank account number changed every time you deposited or withdrew money.
You had to buy a new fridge or freezer (or construct a new larder) every time you brought home new food; or consumed some.
If you had to buy a new car every time you need to top up the tank.
(How would that work when you are driving and using fuel?)

Too real-world for OO programmers to consider relevant?

Then think on this:

Every time the balance in an account object changes; something has to 'mutate': either the current balance changes; or you create a new account object, duplicating all the attributes as the existing one except the balance. And then discard (garbage collect) the old one.

"Spooky action at a distance" is a great quote from a great man about a truly spooky phenomena; and utterly bogus when applied to changing the bit-pattern held at a location in DRAM.

Read only objects are akin to, and equally nonsensical, as read-only variables: the triumph of theoretical dogma over pragmatic practice.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^2: OOP's setter/getter method - is there a way to avoid them? by BrowserUk
in thread OOP's setter/getter method - is there a way to avoid them? by tiny_monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks