mummy
1.0.3
|
move the MethodInstance data structures inside the C# generator class...
search for generated "C" style comments : indicator of "wrapped stuff edge cases"...
make sure that delegates are wrappable function pointer typedefs, not just public function pointer typedefs
address IntPtr <–> I4 issue for 64-bit builds: mummy need to generate different code for 64-bit? generate code that determines IntPtr size at runtime?
error/warning stack: treat warnings as errors, suppress all warnings...
consolidate GetEnumerationTypeString and GetWrappedEnumName
IsReservedMethodName need any more work?
perfect delegate signature generation
eliminate <Chunk> near-copy of code in delegate generation block
eliminate hard-coded 4100/4099 numbers
wrap static methods in iwhUtility classes (there's no reason why we shouldn't / couldn't...)
make enum only classes "root" C# classes – no need to inherit from
perfect the BTX ETX exclusion mechanism (multiple HeaderFileReader objects for parent classes too) for "equivalent to the other wrappers" VTK wrapping...
add hint detection for special method (factory, disposal, register, unRegister) designation
add KWStyle analysis dashboard of source code
enable wrapping deprecated methods? would anybody want this? (right now they are always excluded from wrapping)
how to wrap smart pointers smartly? how does ITK/Java do it?
more build info cached in executable : resource of text output: cvs status of CableSwig/CMakeLists.txt, svn info (for revision of mummy source directory), build environment, development environment version (VS, gcc/cl version), platform environment
shadow classes : another way to implement them besides IDispatch?? existing implementation should really only provide overrides of the methods directly in the class itself depending on parent classes could introduce wrapper dependencies we don't want if the generation of supporting code is conditional based on whether the class being wrapped is a shadow or not
get rid of trailing whitespace in documentation comment blocks??
remove unnecessary comment blocks (saved/old code, now unneeded)
web page / html documentation
document all code (at least all classes and methods) point to MummyApplication::ProcessClass as main entry point of interest document all possible MummySettings.xml values
document assumptions made of hand-crafted base class of generated classes: WrappedObject IDisposable destructor GetCallDisposalMethod GetCppThis ClearCppThis etc.
document "event assumptions"...
write a blurb about performance tests for direct C# array access that explains it requires use of the unsafe C# keyword and use of the /unsafe compiler command line flag