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. | [reply] |
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.
| [reply] |
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)
| [reply]
[d/l] |