taskLiberty Eiffel - Tasks: task #16118, CSV library

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #16118: CSV library

Submitter:  Paolo Redaelli <Tybor>
Submitted:  Sun 06 Feb 2022 09:54:58 PM UTC
 
Should Start On:  Sun 06 Feb 2022 12:00:00 AM UTC Should be Finished on:  Sun 06 Feb 2022 12:00:00 AM UTC
Category:  other Priority:  5 - Normal
Status:  Need Info Percent Complete:  0%
Assigned to:  None Open/Closed:  Open
Fixed Release:  None Planned Release:  None
Effort:  0.00

Wed 09 Feb 2022 08:01:10 AM UTC, comment #3: 

The RFC I referenced covers most of your wishes. Beware of scope creep ;) 

Zwakenberg <hzwakenberg>
Project Member
Mon 07 Feb 2022 06:44:06 PM UTC, comment #2: 

I would even propose to be a bit more flexible :-)  Clearly the referenced RFC should be perfectly parseable, but we should not limit it to that. I have seen so many "CSV" files with a separator ; or <TAB>, and in many situations we have numbers in CSV files, which shall be localizable and use e. g. the "famous" German , as decimal separator.

Some CSV files have a big header section with "an unknown number of lines of bla bla", some have column headers, others not.

All this should ideally be supported and even auto-detected.

So in my eyes we need a few classes to describe the structure of the table, that we can index with a column name. And as we are in an object oriented language it should be easy to create a custom "row" class - for whatever a row represents.

If you ask me, we could make this a nice trial for test driven development: let's agree on a set of example csv files that shall be readable and some interface on how to access the data. And as soon as we have enough failing test cases start to do some coding.

What do you think?

Raphael Mack <ramack>
Project Administrator
Mon 07 Feb 2022 07:43:46 AM UTC, comment #1: 

Indeed, quite a surprise...

We all know what a CSV file is supposed to look like, yet I wonder which of the existing standards we should use for implementation?  The strict RFC-4180 (see https://www.ietf.org/rfc/rfc4180.txt)?  I vote for that one, as this is also the basis for a corresponding web MIME-type.

Zwakenberg <hzwakenberg>
Project Member
Sun 06 Feb 2022 09:54:58 PM UTC, original submission:  

Liberty Eiffel does not offer a Comma Separated Value library.

Paolo Redaelli <Tybor>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ramack (Posted a comment)
  • -email is unavailable- added by hzwakenberg (Posted a comment)
  • -email is unavailable- added by Tybor (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

     

     

    No changes have been made to this item

    Back to the top


    Powered by Savane 3.9