Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Agree, there just doesn't seem to be any point in identifying them Commented Feb 16, 2012 at 8:59
  • This doesn't quite answer the question at all! (No downvotes) Commented Feb 16, 2012 at 12:21
  • 1
    If this is the path they are going to go down, I would strongly consider looking at the MS FxCop/StyleCop tools, as they were, last I knew, inferrence based engines that you could write your own custom rules for, and in order to find EAA patterns directly in source, which might be a shade ambigious to a traditional parser that merely matches symbols, the inferrence engine approach might be quite useful. In evaluation, this limits you somewhat (.Net assemblies); however, the underlying approach and rationale might serve as a good jumping off point. Commented Feb 16, 2012 at 16:15