Allan Rae <[EMAIL PROTECTED]> writes:
| On 14 Oct 2000, Lars Gullik Bjønnes wrote:
| [...]
| > more on FuncSlot... when I first though of this it was as a direct
| > replacement for the string that we pass to dispatch now, it is not too
| > hard to create a FuncSlot that can transfere the type untranslated.
| > It would be a larger implementation because we would need to create an
| > small class hierachy for the types possible to transfere with
| > FuncSlot... all of these would have to have the same root class.
|
| C/C++ Users Journal October 2000 edition has an even better(?) idea using
| templates that is pretty neat (and somewhat larger). They define an
| elaborate template class variant_t and an ArguementList class that uses
| it. It even allows type-safe access to the arguement list (and throws an
| exception if the type you want doesn't match).
|
| That way you can pass anything you like and it doesn't have to be
| derived from some common class.
So this gives just what I described in my toy implementation of
FuncSlot then?
Lgb