Use uint8 for GLchar and GLcharARB. Fix #47. #48
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per discussion in #47 use
uint8
forGLchar
instead ofint8
. Preferuint8
overbyte
because some GL functions, such asglGetString
useGLubyte
rather thanGLchar
.My only hesitation is that this change represents an API change that has the possibility of breaking client code. I expect the majority of use cases to be funneled through
gl.Str
which makes the change transparent but any direct string manipulation will be affected.