Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Rich <rich@example.invalid>
Newsgroups: comp.lang.tcl
Subject: Re: Should I write building blocks?
Date: Sat, 25 Jan 2025 17:10:49 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 31
Message-ID: <vn35up$2u5gf$1@dont-email.me>
References: <20250124203441.7a1b1c34@lud1.home> <vn1nit$2l472$1@dont-email.me> <20250125023706.6b29d7e3@lud1.home>
Injection-Date: Sat, 25 Jan 2025 18:10:50 +0100 (CET)
Injection-Info: dont-email.me; posting-host="c193d54e1ec2d9f9d63f4858590cfbf6";
	logging-data="3085839"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18SXM7gv5ILBOcRjmy8d7Qh"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:pr3H6ETiJlBmAi2d8Yecd5s/HKg=
Bytes: 2255

Luc <luc@sep.invalid> wrote:
> On Sat, 25 Jan 2025 03:59:25 -0000 (UTC), Rich wrote:
> 
>>[1] Don't worry if you don't know what a 'hash function' is right now, 
>>that's not terribly important for this discussion here, and you can 
>>look it up on Wikipedia if you don't know but really want to know.
> **************************
> 
> Hey, I know what a hash function is. I use it all the time to check the
> integrity of ISO images.

I did not know one way or the other -- and what it was was unrelated to 
the topic.

> 
> That was 10 years ago. I wonder if the tcllib implementation has been
> optimized since then.

The current Tcllib version includes a compiled C extension that will be 
built if the Tcllib build finds critcl installed and operable at build 
time.  That will very much optimize hash computations vs. the other, 
pure Tcl, variant in Tcllib.

> Thank you for all the advice.

You are welcome.  Do note that my comments re. "generic interfaces" is 
a very important bit not to miss sight of.  A 'reusable' module is only 
really reusable if you don't have to keep changing the various proc 
arguments for each different use.  So spending effort to boil down to 
the widest common denominator for the "API" (i.e., the proc calling 
arguments) will help with the reusability.