Hi Roy

See updated gist for re-run and module versions.

And, I'm on the list, so no need to copy me directly.

On 17/01/17 10:09, Roy Storey wrote:
Hi Ron,

Thanks for taking the time to have a look. I see you are using 5.20.2,
could it be that your installed modules are not at the same version as
mine? Sorry for not being more detailed in my report. I've updated the
'cpanfile' to lock to specific versions I'm using and removed the
'quote_empty' option as it is only in Text::CSV_XS >= 1.18
<https://github.com/Tux/Text-CSV_XS/commit/f9133e3684f45a6613002f055e3010743d3ea855>
 and
it is not required for this.

I'd be grateful if you could fetch and re-run - without quote_empty
updating modules shouldn't be required (I just ran with Text::CSV_XS
version 1.17 as a check).

Roy

On 17 January 2017 at 10:51, Ron Savage <r...@savage.net.au
<mailto:r...@savage.net.au>> wrote:

    Hi Roy

    I ran your code - unsuccessfully -  and added the output as a
    comment to your gist.


    On 16/01/17 20:54, Roy Storey wrote:

        Hello,

        I'm here looking for help with an issue I'm having with DBD::CSV.

        Specifically, I'm attempting to use the 'after_parse' callback
        to handle
        a csv file with a data defined variable number of columns and hit a
        warning on an attempt to free unreferenced scalar during global
        destruction.

        I've prepared a minimal example at
        https://gist.github.com/kiwiroy/fa0c737ff3f298cb064e554505bc4495
        <https://gist.github.com/kiwiroy/fa0c737ff3f298cb064e554505bc4495>
        so show
        the issue. The two test scripts process the 'input.csv' with
        Text::CSV
        and DBD::CSV respectively and only the latter exhibits the
        behaviour.

        It appears to be 5.24.0 specific. I'm using default perlbrew
        built perls.

        Is there something I'm missing or doing wrong?

        Thanks in advance.

        Roy



    --
    Ron Savage - savage.net.au <http://savage.net.au>




--
Ron Savage - savage.net.au

Reply via email to