Yes could be intresting. :) Tell me how to process (In which way do you want
the fix..)
In fact I do school exersise on it. I have to look inside you source to find
out problems, analyse metric and so on. Removing this class could be intresting
to see dependency with other package..
So do you have any pointer on class that you know there are badly written?
Or do you have some that you are "proud" of it? It could be quite nice to show
a good method.
Thanks in advance
Math
Linus Tolke a écrit :
> Hello Mathieu!
>
> As you have probably noticed the JavaRecognizer.java is generated from
> java.g by ANTLR. The change to a Visitor pattern, is that part of the
> API changes planned for ANTLR 3.
>
> I don't know the reason we have two java.g and generated files. I think
> it is forgotten about by now and I would like if we could remove one of
> them. Would you like to dig into this unify them?
>
> /Linus
>
>
>> -----Original Message-----
>> From: Mathieu Suen [mailto:[EMAIL PROTECTED]
>> Sent: den 22 september 2006 01:45
>> To: [email protected]
>> Subject: [argouml-dev] JavaRecognizer
>>
>> Hi,
>>
>> I was looking how you were implementing language stuff and I found out
>> that you have JavaRecognizer.
>> But it seem to me that is more a parser than a reconizer. BTW I don't
> know
>> what reconizer mean.
>>
>> I how see also that you have 2 JavaRecognizer witch is suprising. Why?
>>
>> I have seen that is a really big class why don't you use a tree to
> analyse
>> Java and so you can apply
>> Visitor pattern. This is fun and you can easily manipulate source.
>>
>> Thanks for answer comment.
>>
>> cheers
>> Math
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
