[Boost-users] Auto dispatch metaprogramming tricks

Subject: [Boost-users] Auto dispatch metaprogramming tricks
From: Alexander Lamaison (awl03_at_[hidden])
Date: 2010-05-21 08:09:49

I would like to dispatch messages to a class based simply on the *presence*
of a message handler method.

Currently, the classes maintain an MPL vector of the messages they handle
and must implement a on(message<MESSAGE_ID>) method for each one.  The
dispatcher uses this compile-time list to build the dispatching code.  This
means the information is maintained twice and may fall out of sync (e.g.
adding the handler but forgetting to update the message vector.

Are there any template metaprogramming tricks I can employ to dispatch the
message to a handler method if it exists and the default handler otherwise?
All this information is available at compile time.  The question is are
templates are powerful enough to make use of it?

Many thanks.

Alex