new abort / kill API

[d4tocchini]

wants:

• n.killPath() kill current path, same thing as else passing down error, stops at nearest continue or tree
• n.killTree(), kills up to nearest tree, through any continue
• n.killContestant() kill execution up to nearest contest, same thing as making contestant lose

By far most useful would be n.killPath.

Not sure about usefulness of killing up to nearest composite, but for that another method name maybe?

Another option would be

n.kill( type )

type in ['path', 'tree', 'composite', 'contest', 'root']

[paulyoung]

Having n.killX() appears to break encapsulation. Could n.abort() bubble up and be handled by whatever ancestor deems itself necessary to handle the error?

[d4tocchini]

Yes, descendent aborts should be handled by an else, which is to say that all aborts would be what I was referring to as killTree - the same thing as if that subTree failed without a catching else

Clearly, abort should only terminate it's current tree & we really don't need different types of aborts because parent trees can decide whether or not they should abort too...

[d4tocchini]

@bergie, this is the top of my wishlist :)

[paulyoung]

I think we can close this one?