Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

Re: RFC: Class::DispatchToAll

by John M. Dlugosz (Monsignor)
on Jul 11, 2002 at 14:56 UTC ( #181037=note: print w/replies, xml ) Need Help??

in reply to RFC: Class::DispatchToAll

As a C++ programmer, I note that some methods work this way, namely destructors and assignment.

I agree with the comment that the "normal" use of supplying your own definition is to override the behavior, not co-operate with multiple versions.

However, I think it would be useful to have an "every parent" dispatch. Each class's implementation works for that (final put-together) class. When you're putting together a new one, you are responsible for coordinating the activity of your direct parent classes; they in turn deal with their parents and members.

Having an every-parent displatch would take the place of "super" which doesn't make much sence in a multiple-inheritence environment.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://181037]
[shmem]: well finally.
[stevieb]: nice! I just finished a GPS "take me home" device last week, and did a bunch of software updates to it yesterday. I also created a pseudo chip with an Arduino to simulate an IC, where it responds to register read/writes over the I2C bus...
[stevieb]: ...from an I2C master. It's ugly and there are many changes I'm going to make, but I had not done anything like it before. It's designed for my RPi:: automated test platform; a system that does CI on *all* my RPi modules.
[shmem]: pseudo chip?

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (5)
As of 2017-06-25 22:38 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (572 votes). Check out past polls.