tcslog-tools 0.1.8

Command-line tools for inspecting tcslog segment files: tcslog-dump and tcslog-dumphdr
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

# tcslog-tools 0.1.7

Documentation and the library requirement. Neither tool changed -- not an
option, not a line of output, and not which stored segment file formats a
build understands -- so a dependent upgrading from 0.1.6 sees no difference
in what the binaries do.

The `tcslog` requirement moves from 0.2 to 0.3. That release replaced
`WriteCallbacks`, a structure of function pointers, with a trait of the same
name, which breaks every caller that writes. These tools do not write: they
take the library with its default features off, so its `write` module is not
compiled here at all, and the requirement moves only because a caret
requirement on 0.2 does not match 0.3. A copy built against `tcslog` 0.2 is
equally correct and goes on working.

The manual's prerequisites and the README now name the version these tools
are built against, and say what that version decides: which stored formats a
build reads follows from the library's version rather than from this crate's.
This is the release that puts both on crates.io.

Requires `tcslog` 0.3.

### Changed

- The `tcslog` requirement becomes 0.3. That release turns `WriteCallbacks`
  from a structure of function pointers into a trait, which is a breaking
  change to the library's writing side -- and these tools do not write: they
  take the library with its default features off, so the `write` module is
  not even compiled here. Nothing in either binary changes, and the records
  they read are the same records, the stored format being unchanged at
  0.1.0.

  The requirement still has to move, because a caret requirement on 0.2 does
  not match 0.3. A build of these tools against `tcslog` 0.2 is equally
  correct and will go on working for anyone who has one; this says which
  release they are built against from here.
- The manual's prerequisites and the README now name the library version
  these tools are built against, and say what that version decides: which
  stored segment file formats a build understands. Neither had named it, so
  the changelog was the only place that said so, and it says it per release
  rather than for the build someone is about to make. The prerequisites
  also account for the `WriteCallbacks` change behind the move, since a
  reader who meets it in the library's own documentation has reason to ask
  whether it reaches these tools. It does not.