---- Reported by eteq 2006-06-20 01:28:49 ----
In line with making the jogl method calls as close as possible to the OpenGL
function calls, maybe the methods with signatures of the form (...,type,int)
(like the glVertex*v or glGenTextures) functions should also be overloaded with
methods of the simpler form (...,type). Admittedly, this, is is just the same
as (...,type, 0), but if its easy to do in gluegen, it might be worthwhile for
the sake of consistancy.
---- Additional Comments From kbr 2006-06-20 23:27:49 ----
This was discussed at length in the JSR-231 expert group. The consensus was that
all of the Java platform APIs which take arrays as arguments (see for example
the java.io.* classes) typically take a tuple of array, offset, and length
arguments. java.nio.Buffers implicitly encapsulate these three concepts with
their notion of a position and a limit. For this reason and for full generality
the APIs in JOGL were universally changed so that instead of solely taking an
array as argument they now take an array and offset since there are no interior
pointers in Java. At this point (for version 1.0 of the JSR-231 spec) this is
not up for reconsideration, although perhaps it could be raised in a subsequent
revision of the specification. For now, closing this bug as "will not fix".
Please discuss the issue on the forums in the future after release 1.0 if you
would like to try to build consensus for making this change. Note also that this
will probably add several hundred additional method overloadings to the GL class
and it is not clear that doing so will add significant functionality.
--- Bug imported by firstname.lastname@example.org 2010-03-24 07:49 EDT ---
This bug was previously known as _bug_ 228 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=228