in reply to Re^4: csv with parens that include commas
in thread csv'ish string with parens that include commas

ascetic:

You asked in the cb why you don't get useful answers.

Actually, you did... but it was an answer to the question you asked; not to the question you really wanted answered.

As to your use of "csv" in the (original; changed without notice) title and your claim (above) that "csv" was useful in the title."

Actually, it was deleterious. If you present the Monks with a question that seems to be about csv, those most likely to answer are those most familiar with csv.

And your node asking "who died and made you CSV God?" is just plain childish, verging on troll-ish.

  • Comment on Re^5: csv with parens that include commas

Replies are listed 'Best First'.
Re^6: csv with parens that include commas
by ascetic (Novice) on Dec 05, 2010 at 03:17 UTC
    It was not the answer to what was asked. Was it helpful or necessary to call my question NO-GO? I use perl in scientific/engineering work, so I am sorry if I am not properly describing CSV. Yes, childish, should have left the no-go comment go without response.
      It was not the answer to what was asked.

      Yes it was (the code proves it).

      Was it helpful or necessary to call my question NO-GO?I use perl in scientific/engineering work, so I am sorry if I am not properly describing CSV.

      Yes. CSV is a known format and there are standard tools for dealing with it.

      Much like dealing with XML-ish data, using standard XML tools is a no-go situation. They will insist on doing their job (like abort because of XML syntax errors) and not DWIM.

      Heck, the following will work for the original question, but it won't for CSV (or the real (and undefspecified) problem)

      $ perl -le"print for split /,/, q!sue,fred,x(mary,jane)!, 3" sue fred x(mary,jane)
        Yes. CSV is a known format and there are standard tools for dealing with it. Much like dealing with XML-ish data,

        The "CSV format" is totally unlike "the XML format" in that there is no single "CSV format definition".

        Whilst the Internet Society took it upon themselves to impose a copyrighted, band-wagon "standard" upon the CSV label circa 2005, the simple expedient of separating data fields by an exclusive delimiter pre-dated that puerile attempt by nearly 40 years.

        Usurping the term and imposing a unilaterally decided definition upon it--and then having the arrogance to copyright it, 38 years after the fact--is exactly as asinine as it sounds.

        Attempting to use that backronistic arrogance to win a pointless argument, gives a whole new connotation to the term pedantic shit.


        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.