Bug #115954 for Text-CSV_XS: How do you detect a parsing error on the last line when using getline?

I'd say use auto_diag. That is by far the safest way to always get the errors. I see you point, and will think about a more robust way to check for the state.

Done some tests (as you could have done too). On error, eof is not set In this file the last line clearly is in error (under default options): $ cat sandbox/test.csv a,b,c,d 1,2,3,4 2,3,4,5 3," "b" ",6,7 $ perl -MText::CSV_XS -MDP -wE'my$csv=Text::CSV_XS->new;open my$fh,"<","sandbox/test.csv";while(my$r=$csv->getline($fh)){say"@$r"};$csv->eof and say "EOF";say for $csv->error_diag' a b c d 1 2 3 4 2 3 4 5 2023 EIQ - QUO character not allowed 5 4 2 As you can see, the error is set, but EOF is not. Feel free to re-open the ticket if you can show me a situation where both error *and* EOF are set due to an error in the final line. Until then, I'll have to close this ticket as not a bug, and will keep with the docs recommendation: my $csv = Text::CSV_XS ({ binary => 1, auto_diag => 1 }); while (my $row = $csv->getline ($fh)) { # ... } $csv->eof or say "auto_diag should have shown you the error already";

At first I thought I was crazy and hadn't encountered what I thought I did. But then I was able to reproduce it minimally: $ cat badcsv.csv 1,bad to the bone,foo 2,"bad "to the" bone",bar 3,""bad to the bone"",baz $ cat badcsv.pl use strict; use 5.010; use Text::CSV_XS; my $csv = Text::CSV_XS->new({ binary => 1, allow_loose_escapes => 1 }); while (my $r = $csv->getline(\*STDIN)){ say "@$r"; } say "EOF" if $csv->eof; say join " ", $csv->error_diag; $ perl badcsv.pl < badcsv.csv 1 bad to the bone foo 2 bad "to the" bone bar EOF 2027 EIQ - Quoted field not terminated 26 3 2

Note that unsetting either "binary" or "allow_loose_escapes" stops EOF from being set. Setting "allow_loose_quotes" or other options don't seem to effect the outcome.