harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Jing Qin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-6636) [classlib][luni]PipedInputStream should not throw exception after the write end close
Date Mon, 20 Sep 2010 14:13:34 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Li Jing Qin updated HARMONY-6636:
---------------------------------

    Attachment: HARMONY-6636-v2.diff

I have added a more readable diff. 
1. Test case both test read() and read(byte[], int, int). 
2. Use isClosed as the flag of write end close.

> [classlib][luni]PipedInputStream should not throw exception after the write end close
> -------------------------------------------------------------------------------------
>
>                 Key: HARMONY-6636
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6636
>             Project: Harmony
>          Issue Type: Bug
>            Reporter: Li Jing Qin
>         Attachments: HARMONY-6636-v2.diff, HARMONY-6636.diff
>
>
> When write end closed first, read end should not throw exception when read.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message