Code review and suggestions for my Code Linting tool.

[Beakerboy]

I have a code Linting tool written in python that targets VBA. I was wondering if anyone would mind reviewing it and offering suggestions of making it better.

Here’s one thing I’ve done that smells bad, but don’t know how to make better.

• My main Linting class passes a new Lexer to each Rule. Each rule then calls getAllTokens(), walks the list looking for errors and reports any found. I’m guessing it would be more efficient to minimize the Lexer creation and walk a CommonTokenStream once. Is there an example somewhere of passing the current stream and doing independent look backs to see (for example) if there is a space before a parenthesis? How would move the pointer to the last element in the stream…Or should I use a completely different approach, like a Listener?
• Any advice on abstracting my work so others can most quickly drop in their own Lexer and Parser and have a Linting tool for a completely different language?