A designated Callback handler for setting the other arguments would be a nice way to go about. It’s long & lengthy, yes – but they’ll be rarely used anyways (I would think).

Line 4 is a bit too weird for me:

element.change += onChange, false, 0, true;

We could try to cut down on those arguments in a couple of ways.

The useCapture Boolean is only relevant to DisplayObjects, and it's unfortunate that useCapture is enshrined in addEventListener() for all events. The event type itself could signal whether useCapture can be toggled or not. I.e., the compiler could know that MouseEvent and other DOM events can bubble. For custom events, useCapture should get out of the way.

Also, it would be great if the useWeakReference default could be set in your event declaration. So you could make your choice and not have to pass three parameters just to change useWeakReference every time.

Simone, while I’d love to overload operators, I’m a (sort-of) mathematician! I am a bit worried what over-zealous library creators would do with the ability to make % stand for anything they like. Code readability is bad enough in the Flash community as it is.

One more thing:

I notice that in editing I didn’t follow through on my Line and Screen argument fully.

I was thinking that in code we do the equivalent of saying “when the line changes, screen should do such and such…”. In this case, ‘changes’ is being used as a verbal noun. The code equivalent is adding an event listener.

Then, when the line actually changes you want to say “the line has changed”. The code equivalent is dispatching an event.

Simone, while I’d love to overload operators, I’m a (sort-of) mathematician! I am a bit worried what over-zealous library creators would do with the ability to make % stand for anything they like. Code readability is bad enough in the Flash community as it is.

One more thing:

I notice that in editing I didn’t follow through on my Line and Screen argument fully.

I was thinking that in code we do the equivalent of saying “when the line changes, screen should do such and such…”. In this case, ‘changes’ is being used as a verbal noun. The code equivalent is adding an event listener.

Then, when the line actually changes you want to say “the line has changed”. The code equivalent is dispatching an event.

so then you can customize how you want to add event listeners

maybe is not a great idea because we don’t end up with a standard solution but I think it will give AS3 developers more freedom.

so then you can customize how you want to add event listeners

maybe is not a great idea because we don’t end up with a standard solution but I think it will give AS3 developers more freedom.