On Fri, Jul 12, 2013 at 10:58 AM, Richard Gaskin <ambassa...@fourthworld.com > wrote:
> t obviates the switch statement. > > We could take this question one step back and ask why we'd want behaviors > at all, when we could just use frontScripts with switch statements instead. > > But that thought experiment (hopefully) makes the case for behaviors clear. > > Nested behaviors simply extend the value of such a mechanism, at long last > giving xTalk one of the most valuable aspects of OOP: subclasses. > I'm definitely not against behaviors themselves, just trying to understand the value of chaining them. Pete lcSQL Software <http://www.lcsql.com> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
