At present, many aspects of the existing APIs which are specified as undefined can actually be defined in a simple way. An illustration could be that, by specification, issuing OpenGL commands when a context is not current to a thread results in undefined behavior. All undefined aspects should be listed, reviewed and defined, and if the definition is not possible, then reasons should be listed. By listing the reasons, it may be possible to further analyze the issue and possibly create alternative data structures and functions, which would not have undefined aspects.
For reference, general issue "Implementation details" is defined as issue no. 32 in the "KSCAF_DocGuidelines" project.
At present, many aspects of the existing APIs which are specified as undefined can actually be defined in a simple way. An illustration could be that, by specification, issuing OpenGL commands when a context is not current to a thread results in undefined behavior. All undefined aspects should be listed, reviewed and defined, and if the definition is not possible, then reasons should be listed. By listing the reasons, it may be possible to further analyze the issue and possibly create alternative data structures and functions, which would not have undefined aspects.
For reference, general issue "Implementation details" is defined as issue no. 32 in the "KSCAF_DocGuidelines" project.