Path: ...!news.roellig-ltd.de!open-news-network.org!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Ashok <apnmbx-public@yahoo.com>
Newsgroups: comp.lang.tcl
Subject: Re: ANNOUNCE: tclcsv 2.4.2 released
Date: Tue, 1 Oct 2024 08:39:00 +0530
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <vdfp4c$2j5rv$2@dont-email.me>
References: <vdek4i$2a8ek$2@dont-email.me> <lm078eFfjcbU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 01 Oct 2024 05:09:01 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="108396557692bdb714488a2b49293f0c";
	logging-data="2725759"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+48jh62UL/MjfofCkPwazc"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:oedQvBU4ZOYdKoNPbkzM+D4/A9Y=
In-Reply-To: <lm078eFfjcbU1@mid.individual.net>
Content-Language: en-US
Bytes: 2214

If you are happy with tcllib's csv, I would suggest keep using it. 
Always easier to distribute Tcl than a binary.

What tclcsv gives you other than speed, is more options for configuring 
the CSV dialect (delimiters, quoting method, headers etc.), a feature to 
guess ("sniff") the dialect, and a Tk preview widget (a la Excel CSV 
import) - see https://tclcsv.magicsplat.com/#tclcsv_dialectpicker

/Ashok

On 9/30/2024 11:29 PM, Ted Nolan <tednolan> wrote:
> In article <vdek4i$2a8ek$2@dont-email.me>,
> Ashok  <apnmbx-public@yahoo.com> wrote:
>> tclcsv 2.4.2 released - update for Tcl 9.
>>
>> The tclcsv extension for Tcl provides a fast and flexible means of
>> reading and writing text files in Comma Separated Value (CSV) format.
>> Includes a UI widget for sniffing CSV dialects.
>>
>> Docs: https://tclcsv.magicsplat.com
>> Download: https://sourceforge.net/projects/tclcsv/files/
>> Repository:https://github.com/apnadkarni/tcl-csv
> 
> I was unaware of this.  When would I use this rather than the CSV package
> in tcllib?  Is it a case of more efficient, or are there other differences?