KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
EGL: unsuitable functions
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
There are API functions which are not suitable to be maintained in the safety environment. For example, core EGL standard specifies both ‘eglGetDisplay’ and ‘eglGetPlatformDisplay’ functions, where having only the second one would simplify the implementation in the safety environment.
For reference, general issue "EGL" is defined as issue #35.
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
Start with the general EGL issue #35 and compare the core EGL functions mentioned here, including eglGetDisplay and eglGetPlatformDisplay. Determine which functions are unsuitable for the safety environment and document the resulting API scope so the implementation can be simplified.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100