Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 27195 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
typedef int8_t GLbyte;
typedef float GLclampf;
typedef uint32_t GLenum;
typedef float GLfloat;
typedef int32_t GLint;
typedef int16_t GLshort;
typedef int32_t GLsizei;
typedef uint8_t GLubyte;
typedef uint32_t GLuint;
typedef uint16_t GLushort;
typedef void GLvoid;
yet, the table at http://developer.xamarin.com/guides/ios/advanced_topics/binding_objective-c/binding_objc_libs/ "Simple Types" recommends binding GL* types to the newly introduced n* native types (e.g. GLfloat to nfloat).
Given that e.g. a GLint is always a 32bit integer, it would make more sense to bind them to a System.Int32. So is this a documentation bug or is there any particular reason why the native types should be preferred? Either way, the documentation needs to change or be amended with reasoning.
Has this been fixed since?