|
From: <Oli...@t-...> - 2003-05-02 23:17:06
|
Hi, Now that my work on Kdevelop adasupport is ebbing down, I finally can come back to xmi2code. Here's what's on my mind: 1. I see that there is a new indenter, I'll look into adapting the Ada generator ot use it. 2. Is it still necessary to be in the xmi2code source directory to invoke the tool? I (and others) have found this to be annoying. If that's still the case then I will start work on making it possible to invoke xmi2code from anywhere. One possibility is to have an env symbol that points to the location where the runtime support is located. And perhaps fall back to a configured location when this env symbol is not set. Further ideas welcome... 3. What do you people think about expanding xmi2code to also handle the reverse path: generate an XMI file from source code? The idea would be that the target language parsers could detect the special comments already generated by a previous xmi2code run, and continue to use those. But for new classes added in the source code only (i.e. that do not have the special comments), new IDs could be generated on the fly. For Java and Ada, we now have ANTLR/C++ based parsers so in principle this would be possible. For C++ and other languages, I haven't looked yet. --Oliver |