Re: primary re-use

[Wes H. <har...@us...>]

>>>>> On Tue, 18 Mar 2003 10:47:00 -0500, Robert Story <rs...@fr...> said:

Robert> I remember that we had a discussion about two primaries (that
Robert> will both be called before a commit) wanting to call the same
Robert> third primary. You came up with a scheme to do this with some
Robert> renaming/prefixing scheme. How does it work?

Robert> ike:   question ikeSaNegPararm -> create_SaNegParam
Robert> ipsec: question ipsecSaNegparam -> create_SaNegParam

add_todos(-remap => 'prefix1', create_SaNegParam);

This will turn all the answers from create_SaNegParam into
prefix1NAME, and will call the action sequence for create_SaNegParam
twice (in this example) magically switching the values before it's
called.  The parent, however, will need to understand that the names
have been messed with and that they should use prefix1 in front of the
qwparam() name.

Warning, it works for simple cases and even a few complex ones.  Where
it will most likely completely die is if you want to do the classic
C++ multiple inheritance tree that boils back down to a single
parent.  (B and C derive from A, but D derives from both B and C).


-- 
Wes Hardaker
Network Associates Laboratories