The previous notwithstanding-- other useful, real-world and everyday examples of "properties with side-effects" might include reading data from a file. You have a property which represents the current line of the file. Reading it may internally clear the buffer and set it up to accept new data.
Or creating a Stack object in which the current Stack Index is brought out as a property, or the number of pages contained within it. Ie. MyStack.PageIndex, or MyStack.PageCount, which you might perhaps agree would be a nice improvement in writing code. Or not-- in which case, there is NO argument for properties of ANY type being "useful", eh? Indeed, why bother to have properties at all? Since all they do in reality, is shield underlying method calls and promote "unexpected side-effects"-- right? ;-) John Whitten -- View this message in context: http://qooxdoo.678.n2.nabble.com/READ-aspect-of-Custom-Properties-HELP-Please-tp7581097p7581104.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
