Hi Andreas! > > For this, it's better to move to Antlr 3 with the classfile grammar, > too. > > How? And why? Just because you want to start anywhere or because you see > any advantages in a Antlr 3 grammar?
No functional advantages. Just the usual maintanence process when a used framework moves to a new version. (However, in the meantime I feel more familiar with the Antlr 3 grammar than with the old one.) > > The basic idea of merging source and classfile RE into one module is > > great. Should it be possible to both import .class and .java files at > once? I > > think this is not necessary... > > What do you want to achieve? I thought about the classfile RE as a way to > include > lib interfaces easily in a diagram. It was not really meant to support > full > roundtrip engineering and to actually work on jars in Argo. Java OTOH > should > support full RTE, so you can actually modify the sources in Argo. So it's > critical that a imported classfile never overwrite the same class, if it's > also available as a source file. Full RTE? That's not the intention behind the argoum-java, IMHO. The C++ module states this as a goal on the project homepage, yes, but I will not do that for Java (maybe others). The reason for putting it into the argouml-java module is just to bundle everything that supports Java as the target language in one module. OK, even more important is to get all Java stuff out of the core project, which indeed permits different Java supporting modules, no problem with that. I just like to have a single module will all Java support in one module, and let the user decide how he uses its functionality. That's why I would separate source file import and classfile import. Maybe one first imports some key frameworks as jar files, and then the sources that uses these frameworks. Makes no sense to import class file for which sources are available, but if the user wants it... (but not in a single step, please) After some thinking, I don't mind to bundle different parsers (Antlr 2+3 based) in one module that support source RE, class RE, CG and notation, all for Java. Only, that would look a little weird if someone looks in it's used libs, and that's why I lightheartedly said "it's better to move to Antlr 3 with the classfile grammar". Or do you have other reasons why we should not integrate class and source RE in one module? Let's think from the users perspective (technically everything is possible, thanks to the disjunct packages of Antlr 2 and 3). Luckily, we're not in a hurry... Thomas -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
