This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug awt/20630] Image APIs should use BufferedImage exclusively
- From: "sven at physto dot se" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 4 Aug 2005 05:05:02 -0000
- Subject: [Bug awt/20630] Image APIs should use BufferedImage exclusively
- References: <20050324221259.20630.fitzsim@redhat.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From sven at physto dot se 2005-08-04 05:04 -------
(In reply to comment #2)
Apparently I was wrong; DataBuffer does indeed wrap a true Java array. E.g. With
the JDK, if a DataBuffer is constructed from a java array, changes in that array
will be reflected in the DataBuffer. Same goes for the array returned by
Databuffer.getData().
So this appears to be a bit of a conundrum. Perhaps DataBuffer could represent a
*pinned* java array, with the databuffer constructor pinning the array from the
native side and the destructor unpinning it? Is that legal? This won't help if
the array pointer returned by JNI is a copy though. Problematic.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20630