On Wed, Jun 4, 2008 at 6:01 AM, "Andreas Rückert" <[EMAIL PROTECTED]> wrote:
> In my view, the current [c++] RE simply doesn't work for most existing > projects. > Almost anyone declares the classes in the header files, and since the include > statements are ignored, but the parser requires to know every type in the cpp > file, RE of any real-world app will fail. We want to make our reverse engineering as comprehensive as possible, but we also should have a goal of making it robust enough to be able to extract useful information from a partial set of sources/libraries. I know this is an issue with Java RE and it sounds like it may be with C++ as well. 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. Note, this isn't saying anything about whether we should/shouldn't be incorporating the JCPP dependency at this late date in the development cycle. That's primarily a risk/benefit decision. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
