I don't especially want to
step on the toes of Benjamin Kowarsch and his colleagues, but I
think it in addition to what I've already done with CardBitOps
library, might be worth the trouble to hoist several other
elements of the M2BSK library to separate projects, to make it
easier to apply them to other projects beyond both M2BSK itself
and those I am already working on.
I don't suggest this lightly, if for no other reason than that it
puts me in the position of being the key figure in maintaining
several libraries. However, I suspect that others would benefit
from doing this.
What I propose is creating the following library projects,
arranged by common topic, and omitting those which are specific to
M2BSK:
* General integer math - containing the CardMath, IntMath, and
LongIntMath modules.
* Bit manipulation - Containing the CardBitOps, IntBitOps, and
LongIntOps modules.
* Char - containing the Char, AOC, ISO646, Newline, Tabulator, and
String modules.
* File system
interface - BasicFileIO, FileSystem, and Fileutils modules.
* Console - containing the Console module (with the
procedure BusyRead from Terminal incorporated here, possibly under
a new name such as ReadCharUnbuffered).
By applying these as separate Git repos, they can easily be added
as sub-modules to any Git project which needs them, or if not,
they can be manually added to a given project as needed.
Does this make sense, or am I making too much of all of this? Are
there any changes in or additions to the organization I am
proposing?