Am 13.07.2017 15:38, schrieb Donald G Porter:
> The clock speedups are in need of substantial review, and they are> struggling to find enough time among a knowledgeable set of reviewers.
Well, it was already thoroughly reviewed from some people (e. g. from
Jan), and I've already
eliminates all bothering things (that I got listen).
IMHO, all the people, that cannot "find enough time" but tell us that
the patch is dangerous
because ... (I did not hear which is why), could either find the time or
just accept it as is. IMHO.
> The patch came in touching far more pieces of Tcl and associated> packages in far more radical ways than I think anyone was expecting.
I would really like to know more about a "radical ways"...
BTW this branch was created as speedup bounty, and if developer
optimizes C-api
of clock-engine, but he notes hereafter that the rest of tcl has
attracted handbrake
(msgcat, ensembles, etc), and the developer is able to fix it by the
way, he just does it.
Why not?
As already suggested, I am in favour to extract my new clock-engine into
separates
tcl binary module, that just overwrites clock-ensemble on demand.
But flightaware doesn't want it. Or...
@Peter, @Karl My offer still stands... Let us just rewrite it as module.
Unfortunately, this is a very thankless employment to participate in
bounties, where tcl-core touched.
I really regret to have done this. Just because I've many other
projects, where I can better and more
productive spend my time.
And it looks like I've not learned anything, because I do it again and
again (see for example my
last event-perf-branch with TIP-302 implementation).
Regards,
Sergey
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Tcl-Core mailing list
Tcl-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tcl-core