Skip to content
New issue

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

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

Already on GitHub? # to your account

Naked immediate values #45

Closed
MatthewHambley opened this issue Mar 24, 2022 · 0 comments · Fixed by #76
Closed

Naked immediate values #45

MatthewHambley opened this issue Mar 24, 2022 · 0 comments · Fixed by #76
Labels
enhancement New feature or request new rule Add a new rule

Comments

@MatthewHambley
Copy link
Collaborator

When dealing with multi-precission software it can be important to know exactly what the developer means when they type 42. Do they mean 42_r32 or 42_r64? A rule which throws errors for unspecified immediate values would detect this.

Individual control of integer and real behaviour would probably be best. There is no need to consider logicals as I've yet to come across a situation where it made sense to think about different precisions of 1 bit value.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request new rule Add a new rule
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant