From: Erik L. <el...@xs...> - 2024-11-27 22:44:46
|
Thanks for the by and large positive reception of my proposal. @Steve, regarding the encouragement to remain cross-platform ------------------------------------------------------------ Sure, that's what I want too (why wouldn't I ?). Various of my previous contributions to bug tickets were reported/tested only on Linux and Windows, because I didn't have a macOS system available. Also, as far as compiled code is concerned, I don't master objective C. Therefore, this limits my possibilities for remaining entirely cross-platform. For the short term (subjects A. and B. of my proposal), this seems to be a moot point because these subjects are platform-indifferent, script-level tasks. However, for subjects C. and D. this will be something to be dealt with (occasionally). In anticipation of working more regularly on Tcl/Tk development, I got myself a macOS machine, so that I can at least run tests locally (against a pre-compiled Tcl/Tk) on that platform. General procedure ----------------- I'm going to make a start with subject A.1 (see below for the entire subject A). My development efforts will happen intermittently at an order of magnitude of a week (currently two weeks on, one week off), because of my private situation. Therefore, it may take a few weeks before anything is ready for a first commit. Would you like me to report back here when that moment arrives (in order to create an appropriate branch in the Fossil Tk repository) ? Best regards, Erik Leunissen. -- A. STRUCTURAl ASPECTS OF THE TK TEST SUITE ------------------------------------------ A.1 Collect utility procs A.2 Collect (more) test constraint definitions in constraints.tcl A.3 Make internal structure of test files uniform A.4 Use common names for certain types of common utility procs -- |