Comments on: Circuits: event driven components.

By: James Mills

James Mills — Thu, 12 Feb 2009 05:38:51 +0000

The operator overloading is all optional of course.
You -can- just simply call the register() method of a Component.

–JamesMills

By: James Mills

James Mills — Thu, 12 Feb 2009 00:38:51 +0000

The operator overloading is all optional of course.
You -can- just simply call the register() method of a Component.

–JamesMills

By: jnoller

jnoller — Sun, 01 Feb 2009 12:38:33 +0000

I agree – metaprogramming and operator tweaking really obscures things – sure, it makes it more compact, but there's a threshold where compactness begins to push usability/clarity down.

By: Jack Diederich

Jack Diederich — Sun, 01 Feb 2009 04:51:33 +0000

Yes, a little too much metaprogramming. Because dog_instance.sit() is never called as such you have to wonder what magic calls it: is the the fact that the channel gets passed 'sit' or because the event class is named 'Sit(Event)'. A simple run_event method in Sit that calls whatever.sit() would clear things up. The trackbacks would be nicer too.

I also have a healthy fear of operator overloading. What do the following mean?
manager1 += event1
manager1 = manager1 + event
manager1 += event1 + event2
manager1 = manager2 + event1

If '+=' is an alias for manager1.register() then just kill it. Everyone understands function calls so use em.