[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bugs #9108] ByteBuffer.compact doesn't always set limit to capacity
From: |
anonymous |
Subject: |
[bugs #9108] ByteBuffer.compact doesn't always set limit to capacity |
Date: |
Thu, 27 May 2004 02:44:25 -0400 |
User-agent: |
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461; .NET CLR 1.0.3705) |
This mail is an automated notification from the bugs tracker
of the project: classpath.
/**************************************************************************/
[bugs #9108] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9108>
Project: classpath
Submitted by: 0
On: Wed 05/26/04 at 06:11
Severity: 5 - Average
Resolution: None
Assigned to: None
Status: Open
Platform Version: None
Summary: ByteBuffer.compact doesn't always set limit to capacity
Original Submission: According to the Sun Javadoc, and observed Sun JDK1.4
behaviour, the compact method always sets limit to capacity. In the Classpath
implementation ByteBuffer.compact only sets limit to capacity when the position
is not 0.
For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9108>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bugs #9108] ByteBuffer.compact doesn't always set limit to capacity,
anonymous <=