comment on

I agree much with you Grandfather, however he stated in his post-

When I run the script on my input.csv file the output.csv file which is created by the script has double quotes in two of the data columns, i.e. the Timestamp field "2018-01-23 00:00" and the ProdDescription field "Acme Widget Large 20 inch" These double quotes need to be removed to comply with the required data format of the final csv file.

So I don't know if he sends the result somewhere, they will be able to parse a proper CSV file.

Needed additions/changes to the script to make it proper would be:

Add use Text::CSV; in the header with the other use statements.

Create a new csv object, my $csv = Text::CSV_XS->new({binary => 1, eol => $/}); before the while loop.

Instead of the print statement, use $csv->print($out, [ @tmp{@cols} ]);.

In reply to Re^3: Modifying an existing Perl script to ask for input and output filenames and also remove double quotes for outfile file by Cristoforo
in thread Modifying an existing Perl script to ask for input and output filenames and also remove double quotes for outfile file by ei6eqb

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks