commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Neidhart (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (COLLECTIONS-397) BoundedFifoBuffer could allow null entries
Date Sun, 17 Mar 2013 12:05:14 GMT

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

Thomas Neidhart resolved COLLECTIONS-397.
-----------------------------------------

    Resolution: Won't Fix

BoundedFifoBuffer will be removed in favor of java.util.concurrent.ArrayBlockingQueue, see
COLLECTIONS-432.
                
> BoundedFifoBuffer could allow null entries
> ------------------------------------------
>
>                 Key: COLLECTIONS-397
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-397
>             Project: Commons Collections
>          Issue Type: Improvement
>            Reporter: Sebb
>
> BoundedFifoBuffer could easily allow null entries - it uses an array for storage.
> Is there any reason why nulls should not be (optionally) allowed?
> This would mean changing the remove() implementation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message