Re: What was intended with 'cascade' [Bug 499, cascade prematurely ends traps]

On Thu, 2004-03-11 at 21:24, Jeff Buhrt wrote:
> Charlie implied it should be like Lithium

Which is that you can call 'cascade = v' in the middle of a trap, which
defers to the chain of traps before returning to finish off the trap.

> ...but this comment from Adam says otherwise:
> http://marc.theaimsgroup.com/?l=xwt-core&m=106422545315218&w=2
> Basically it says cascade is a property vs a function like it was in Li.
> [I assume thus *not* being a function call.]

This doesn't imply a change in behaviour, just a change in syntax:

'arguments.cascade()' becomes 'cascade'
'arguments.cascade(v)' becomes 'cascade = v'

It's just cleaner and more inline with the notion of traps.
-- 
- Charlie

Charles Goodwin <[email protected]>
Online @ http://www.charlietech.com