Sujet : Re: Should I write building blocks?
De : rich (at) *nospam* example.invalid (Rich)
Groupes : comp.lang.tclDate : 25. Jan 2025, 18:10:49
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vn35up$2u5gf$1@dont-email.me>
References : 1 2 3
User-Agent : tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
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.