Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need a COM Analyzer for chained member access #4032

Closed
bclothier opened this issue May 24, 2018 · 1 comment
Closed

Need a COM Analyzer for chained member access #4032

bclothier opened this issue May 24, 2018 · 1 comment
Labels
difficulty-03-duck Involves more challenging problems and/or developing within and revising the internals API rubberduck-analyzer-project technical-debt This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.
Projects
CodeName: Cucumber

Comments

@bclothier
Copy link
Contributor

With PR 3975, we introduced an analyzer project to help us validate some of RD's specific needs and thus automate code quality review in this manner.

The main impetus behind this was to help manage COM interaction which is often a source of memory leak or access violation. Though we have a couple analyzers already, we are missing the most common source -- chained access across safe COM wrappers class -- those will leak and thus must be alerted as an error to require that RD contributors manage the access carefully, using using or local variables depending on the situation.
@bclothier bclothier added meta technical-debt This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point. difficulty-03-duck Involves more challenging problems and/or developing within and revising the internals API labels May 24, 2018
@bclothier bclothier added this to TODO in CodeName: Cucumber via automation May 24, 2018
@comintern comintern moved this from TODO to In Progress in CodeName: Cucumber Jul 31, 2018
@bclothier
Copy link
Contributor Author

This was already addressed in PR #4238 / #4378 - closing.

CodeName: Cucumber automation moved this from In Progress to Done Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
difficulty-03-duck Involves more challenging problems and/or developing within and revising the internals API rubberduck-analyzer-project technical-debt This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.
Projects
CodeName: Cucumber
  
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bclothier @retailcoder