Hi Luis!

> Does ANTLR 3 use a different package? If not I think this will be 
> difficult, since, AFAIK, the classloader is the same for ArgoUML core 
> and the remaining modules.

The Antlr jar file antlrall.jar need to be replaced. Since it belongs to the 
core of ArgoUML and other modules depend on it, it must stay. So, there must be 
found a way for the new Antlr 3 based Java import, to use it's own Antlr jar 
instead of the existing one, both for the build and at runtime.
(Later, there could be an approach to move Antlr away from the core.)
I'd definitely need help here!

> Also, will we get an update of the classfile reveng grammar? It would be 
> nice if that would be updated also to keep consistency amongst the java 
> reveng functionality.

I have not planned to do so, as I'm not familiar with that grammar. Andreas, 
you contributed it, would this be difficult? Can you give me a hint so that I 
could deal with it?

> In the C++ module, David Wigg posted a new version of the grammar for 
> ANTLR 2.7.7. The current version which is ported to java and used by the 
> C++ module didn't had problems with the recent update from ANTLR 2.7.2 
> to 2.7.7. I think that this will be different when upgrading to 3.0.x...

Definitely. Many Changes!

> But, I may give it a try after finishing the work I'm doing in the 
> profile subsystem.

The problem here is, that there is no C++ grammar for Antlr 3 so far, I think. 
For Java I found one, so my (nontrivial) task is to put the ArgoUML code into 
it. For the C++ grammar the approach could be different: change the current C++ 
grammar with ArgoUML code in it so that it could be processed by Antlr 3. 
Requires deeper Antlr knowledge, and the result would not be a Antlr 3 
optimizes grammar.

My suggestion: For C++, stay with Antlr 2.7.7 (unless someone comes up with a 
C++ grammar newly written for Antlr 3), and let us benefit from it by setting 
up a working enwironment with both Java and C++ import based on two different 
Parser generators! Would be a nice showcase to prove that ArgoUML import 
functionality is independent from a certain parser generator.

Regards,
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]

Reply via email to