#77 dodo not generating try/catch block for extended interfaces

closed
nobody
None
5
2004-06-02
2004-02-26
Jim Trainor
No

Extended COM interface methods generated by dodo are
missing try/catch blocks.

For example, look at the IAAFTypeDefVariableArrayEx
methods implemented (generated by dodo) in
CAAFTypeDefVariableArray.cpp, and the
IAAFMasterMobEx methods in CAAFMasterMob.cpp.

It would be good to repair this for the 1.0.2 release.

It must be repaired for the 1.1 because several new
extended interfaces will be added.

Discussion

  • Jim Trainor
    Jim Trainor
    2004-02-27

    Logged In: YES
    user_id=239292

    The problem is not restricted to extended interfaces.

    It exists where ever the dodo AD_COM_METH is used to add
    methods of secondary interfaces. For example, CAAFHeader
    mixes in the IAAFHeader interface and implements
    IAAFHeader::GetStoredByteOrder() in
    CAAFHeader::GetStoredByteOrder(). That method is also
    missing a try/catch block.

    AD_COM_METH is used in:

    AAFEssenceAccess.dod
    AAFHeader.dod
    AAFMasterMob.dod
    AAFSourceMob.dod
    AAFTypeDefVariableArray.dod

    ... all the mixed in methods do not have try/catch blocks.

     
  • Jim Trainor
    Jim Trainor
    2004-03-03

    • summary: dodo not generating try/catch block for extened interfaces --> dodo not generating try/catch block for extended interfaces
     
  • Jim Trainor
    Jim Trainor
    2004-06-02

    • status: open --> closed
     
  • Jim Trainor
    Jim Trainor
    2004-06-02

    Logged In: YES
    user_id=239292

    Resolved in main for the V1.0.2 release.

    Changes were made to the AAF/dodo/macros/exp.mac file.

    The affected (dodo generated) AAF/ref-impl/src/com-api files
    were also commited.

    Must be merged to rosebud.