Right as usual.
This is pretty much a standard memoization pattern where there are
methods that need to clear the memoization as a side-effect. We could
either have the 'dirty' flag as you propose, or the side-effecting
methods could just clear the cache (so that it definitely does not
match to new value).
On 2008-08-08, at 14:33EDT, André Bargull wrote:
If possible, we want to get rid of the second argument, for example
by adding an internal flag [1].
[1] http://www.openlaszlo.org/pipermail/laszlo-dev/2008-July/016387.html
Hi Tucker,
I'm modifying the components to take advantage of the <setter> tag.
What did we decide to do with setters that take more than one
argument. Examples:
function lz.view.setX ( v, force = null)
function lz.view.setX ( v, force = null)
function lz.text.setText ( t, force = null)
Thanks!
Phil
