commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CSV-61) CSVFormat combines input and output settings in a single class; might be clearer as separate classes
Date Wed, 14 Mar 2012 19:20:42 GMT

    [ https://issues.apache.org/jira/browse/CSV-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229522#comment-13229522
] 

Sebb commented on CSV-61:
-------------------------

Applications that read CSV files don't necessarily want to write them and vice-versa.

Separating the configurations would allow them to be used independently.

It might be a bit different if the same format definitions were used for input and output
(as for DateFormat), but they are not, and I suspect that would not be possible.
                
> CSVFormat combines input and output settings in a single class; might be clearer as separate
classes
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CSV-61
>                 URL: https://issues.apache.org/jira/browse/CSV-61
>             Project: Commons CSV
>          Issue Type: Improvement
>            Reporter: Sebb
>
> CSVFormat currently includes both input (parsing) and output (formatting) settings in
a single class.
> This is a bit confusing; for example lineSeparator could be either.
> (The Javadoc has now been corrected)
> It might be clearer to have separate classes for input and output.
> This would also reduce the number of parameters in each ctor.

--
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

        

Mime
View raw message