You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Thomas Neidhart (JIRA)" <ji...@apache.org> on 2013/03/17 13:05:14 UTC

[jira] [Resolved] (COLLECTIONS-397) BoundedFifoBuffer could allow null entries

     [ 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