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

[Feature Request] Problem for Enum #13

Open
zhenyu-zhou opened this issue Dec 5, 2016 · 0 comments
Open

[Feature Request] Problem for Enum #13

zhenyu-zhou opened this issue Dec 5, 2016 · 0 comments

Comments

@zhenyu-zhou
Copy link

zhenyu-zhou commented Dec 5, 2016

I find that, if a data structure contains enum field, such field won't be made symbolic although I tried to make all fields symbolic.

I totally understand enums are (immutable) objects and cannot be handled directly. And currently I have several makeshifts for this:

  1. Add a wrapper for the target function.
    Such wrapper has an integer parameter, which allows the SUT to assign different enum types accordingly. If we change the target function to this wrapper and make the integer parameter symbolic, the enum can be "symbolic" as well.
  2. Add an integer field in the data structure to control the enum type accordingly.
    This may require a deep modification for the SUT. I myself don't prefer it.
  3. Call getTypeValue() to convert enum to its integer value.
    Then it seems to work for me - the underlying integer value could be symbolic.

Please let me know whether I'm on the right way for this issue or if you have any more suggestions.

Perhaps the documentation can contain such guidance as well? (Please let me know if it already talks about such issue.)

Thanks!

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

2 participants