On Tue, Apr 28, 2015 at 10:14:07AM -0400, Carl Traenkner wrote: > Now (well 2.12b anyway) I get two instances of inner sort of... I > get innerType and innerType1. But now to use this I have no predictable way > to pick the inner type names. It would be great if I could specify a switch > so the inner class names were based on the hierarchy and it auto generated > classA_inner and classB_inner or something along these lines so I would > know what the names are and could even generate the name... >
Sigh. When will I learn to read a question/message more carefully? Please ignore that message yesterday. Because I've struggled so much with that problem of duplicate names in multiple namespaces, my head gets stuck on that issue. OK, about the need you describe for predictable names for those inner classes -- Currently, those names are created in process_includes.py, which is imported and used by generateDS.py. It happens in function raise_anon_complextypes. One possible solution is to allow the user (you) to provide a table that maps the name of the inner type and the name of the type definition that contains it onto a name of your choice. I've made a few changes that almost do that, but it needs work and bullet-proofing. Tomorrow, I hope to have a fix that you can try out and comment on. Dave -- Dave Kuhlman http://www.davekuhlman.org ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ generateds-users mailing list generateds-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/generateds-users
