From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29745 invoked by alias); 4 Aug 2005 05:05:02 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 29726 invoked by uid 48); 4 Aug 2005 05:05:02 -0000 Date: Thu, 04 Aug 2005 05:05:00 -0000 Message-ID: <20050804050502.29725.qmail@sourceware.org> From: "sven at physto dot se" To: java-prs@gcc.gnu.org In-Reply-To: <20050324221259.20630.fitzsim@redhat.com> References: <20050324221259.20630.fitzsim@redhat.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug awt/20630] Image APIs should use BufferedImage exclusively X-Bugzilla-Reason: CC X-SW-Source: 2005-q3/txt/msg00171.txt.bz2 List-Id: ------- 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