Immediate-Mode-UI / Immediate-Mode-UI/Nuklear
Why c89? Why not c99 or c11?
- Dominant language
- C
- Stars
- 11.4k
- Forks
- 686
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 3
Description
Honestly curious about the decision to stick with c89. I understand that c99 had some flaws that prevented certain projects from adopting (Eg Linux kernel), but c11 has definitely fixed a bunch of stuff and provides nicer facilities for variable scoping to help remove bugs (eg Linux kernel allows c11). Plus, more and more people are getting involved with C in a post c99/c11 world. So further development assistance would feel more natural if we could push for a newer version.
What is the reason that nuclear mandates c89?what is the ethos behind sticking with this?
Contributor guide
Research direction
The issue mentions no files, tests, or entry points. Start by reviewing the repository’s stated C89 requirement and the compatibility implications of C99 or C11; done would be a documented project decision about whether the language standard should change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100