41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
-
+
|
- **Header file restructuring.** The current separation of the APIs into many `include/fossil-scm/*.h` files is somewhat confusing. The initial intent was to keep my low-end development system of the time from choking on syntax highlighting on one large file, but those days are largely behind me. It may make sense to combine those into 1 public API file, 1 internal API file, and the auto-generated config file(s). (Even then, it's big enough to choke emacs' syntax highlighting on lower-end systems like Raspberry Pi SBCs.)
- **Stop using char as booleans**. This tree historically uses `char` type for booleans. Now that the tree is C99, we can switch to the `bool` type.
- **Port over the `XDG_CONFIG_HOME`-related changes** for finding the global config db.
- Update [the fossil file format docs](https://fossil-scm.org/home/doc/trunk/www/fileformat.wiki) to document the handful of special cases not covered there, like the convention that tag names must not be purely hexadecimal and control artifacts may not contain tags which refer to that control artifact (like a checkin may legally do (and often does)).
- Update [the fossil file format docs](https://fossil-scm.org/home/doc/trunk/www/fileformat.wiki) to document the handful of special cases not covered there, like the convention that tag names must not be purely hexadecimal and control artifacts may not contain tags which refer to that same control artifact (i.e. self-referential tags, like a checkin may legally do (and often does)).
# Maybe (and Maybe Not) TODO
- **Undo** support.
- **Symlinks**. i have always disagreed with the addition of symlink support into fossil: platform-specific constructs simply have no place in the core of any SCM. For platforms which don't support symlinks, fossil stores/manages them as plain text files with a single line holding the name of the referenced file. This is *very likely* the route the library will take, especially since the hassles symlink handling caused fossil in late 2020 (long story). Probably the only way the library will support proper symlinks is if someone who uses that feature adds it.
|