Hi! -------- Original-Nachricht -------- > Datum: Wed, 4 Jun 2008 15:45:59 -0400 > Von: "Tom Morris" <[EMAIL PROTECTED]> > An: [email protected] > Betreff: [argouml-dev] Reverse Engineering partial code bases
--<snip>-- > In a many cases, we can tell from the context that an identifier is as > a Class or Interface or some other specific type. In cases where we > can't tell, we should defer guessing as long as we can and then make > the best interpretation possible with the available information. > Can't tell whether it's a Class or an Interface? Call it a > Classifier. That will at least make use of the information we have > available. Ok, how do you implement this? The parser throws an exception and then you start analyzing the code, what may caused the problem? How? The C++ parsing is a PITA, and I want to avoid touching the grammar at almost any cost. In my eyes, we should use the existing grammar, add all the productions, that are absolutely necessary and make sure, that the parser runs through, if the code compiles, and leave it at that. --<snip>-- Ciao, Andreas -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
