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

Support bitfields and bitmasks #198

Open
fwendland opened this issue May 25, 2021 · 0 comments
Open

Support bitfields and bitmasks #198

fwendland opened this issue May 25, 2021 · 0 comments
Labels
enhancement New feature or request mark Concerns MARK files in Codyze

Comments

@fwendland
Copy link
Collaborator

Software libraries may use bitfields and bitmasks to track configuration options. Options can be included, combined or excluded. In the end, there will be a bitfield with each bit representing whether an option is set or not.

Currently, MARK does not support a simple way to track bitfields and bitmasks. In particular, it must be possible:

  1. to track expressions (i.e. &, |, ...) that combine options,
  2. to track multiple calls to function manipulationing options (e.g. set_*(), unset_*(), ...)
  3. to track calls that reset options (e.g. clear_*())

In the end, it should become possible to get a computed value for the bitfield before it's being used.

@fwendland fwendland added enhancement New feature or request mark Concerns MARK files in Codyze labels May 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request mark Concerns MARK files in Codyze
Projects
None yet
Development

No branches or pull requests

1 participant