"behavior of a program is undefined" vs "program has undefined behavior"
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
Sometimes we has "A program has undefined behavior", and other times we say "the behavior of a program is undefined".
As far as I can tell, these two alternate wordings mean exactly the same thing, and it would be good for consistency to pick just one form.
I suggest changing all "program is undefined" forms to the "has undefined behavior" form for the meta-reason that it puts the words "undefined behavior" together, making it easier to turn that term into a macro like "implementation defined", with a long term view to create an annex or index of undefined behaviors built on such a macro.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. Search the draft sources for both quoted formulations, inspect each occurrence for context, and standardize equivalent wording while preserving cases where the meaning differs. Done means the draft consistently uses the selected form; no validation command is mentioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100