Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 27 Mar 2012 00:43:26 +0000 (UTC)
From: "Sebb (Resolved) (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <506060744.21087.1332809006457.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <955498941.20824.1332806613840.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CSV-87) CSVParser.getRecords() returns null
 rather than empty List at EOF
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sebb resolved CSV-87.
---------------------

    Resolution: Fixed
    
> CSVParser.getRecords() returns null rather than empty List at EOF
> -----------------------------------------------------------------
>
>                 Key: CSV-87
>                 URL: https://issues.apache.org/jira/browse/CSV-87
>             Project: Commons CSV
>          Issue Type: Bug
>            Reporter: Sebb
>
> CSVParser.getRecords() returns null rather than empty List at EOF.
> It's usually easier for applications to deal with empty lists than to have to check for null after every invocation of the method.
> If the application really does need to know if the list is emty, then it can use a method such as isEmpty().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira