On 07/01/2013 16:53, Marvin Humphrey wrote:
I see. To avoid a DRY problem where we duplicate the code which generates callbacks.h in every host except C, we want to put the code in a common location. Sounds good.With that clarification in mind, I'd like to reaffirm my support for option number 2: 2. Let the host language code in CFC trigger the creation of callbacks.h. This would probably mean to instantiate another temp CoreBind object in the host language code for this task. CFCBindCore seems like a fine place to put the common code. The temp object is no big deal, since we're just going to reuse the CFCHierarchy object.
Yes, I think that's the best solution. Creating CFCBindCore and CFCBindClass objects is cheap.
Nick
