[commit-cp] [bugs #9108] ByteBuffer.compact doesn't always set limit to capacity

[Michael Koch]

This mail is an automated notification from the bugs tracker
 of the project: classpath.

/**************************************************************************/
[bugs #9108] Latest Modifications:

Changes by: 
                Michael Koch <address@hidden>
'Date: 
                Mit 17.11.2004 at 09:08 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
            Category | None                      | classpath
         Assigned to | None                      | mkoch







/**************************************************************************/
[bugs #9108] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9108>
Project: classpath
Submitted by: 0
On: Mit 26.05.2004 at 10:11

Category:  classpath
Severity:  5 - Average
Resolution:  None
Privacy:  Public
Assigned to:  mkoch
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/