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.

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

Make collection of expressions per file configurable #2

Open
clhunsen opened this issue Sep 19, 2014 · 0 comments
Open

Make collection of expressions per file configurable #2

clhunsen opened this issue Sep 19, 2014 · 0 comments
Milestone

Comments

@clhunsen
Copy link
Collaborator

Right now, during the execution of the 'general' analysis, for each file all #ifdef expressions are collected, but each distinct expression is only collected once per file (comparison via string equality).
see: analyses/general.py, function _wrapFeatureUp()

This should be configurable to affect the construction of these local (per-file) pools.
Like: --localpool [once_per_file | once_per_project | all]

  • once_per_file
    • collects each expression once per file
    • per-file-redundant expressions are removed
    • (same behavior as before)
  • once_per_project
    • collects each expression once per project
    • all redundant expressions are removed
  • all
    • collects all expressions per file
    • no expressions are removed
@clhunsen clhunsen self-assigned this Sep 19, 2014
@clhunsen clhunsen added this to the 0.8.5 milestone Sep 19, 2014
@clhunsen clhunsen removed their assignment Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant