Regenerate at 0834b29, for the three API gaps the examples exposed
CDecoder gains tryReadEncodedValue(), the status-returning form of
readEncodedValue(). COctet gains secureClear(). EDecoderStatus's example
no longer classifies the length octets by hand -- which it had to, because
until this commit no public API produced the enum -- and instead drives a
real incremental read loop.
Every other page changed only in its commit stamp, which is what the stamp
is for.
Add the generated API reference, and the pages Home already linked to
173 pages, one per public class, struct and enum, plus an API-Reference
index grouped by module. The reference half of each page is generated by
tools/wikigen.py out of the headers' Javadoc -- nothing is retyped -- and
every page records the commit it came from and links to its own header.
That stamp is the whole mitigation for a wiki not being versioned with
the code: a stale page can be regenerated, and says which commit it came
from so a reader can tell that it is stale.
The example on each page is hand-written, lives in the repository under
examples/wiki/, and is compiled and linked by the certpp_example_wiki
build target before it is published here. A published example that has
never been compiled is a guess. Every one of the 173 types has one; the
generator reports any type that does not.
Home.md linked to Integration-Guide, FAQ and Troubleshooting, none of
which existed. They do now, and they are hand-written on purpose: they
cover what outlives any one version of the code -- how to consume the
library, which parts are constant-time and which explicitly are not, what
performance to expect and why signatures are currently slow, and the
failures people actually hit. Home.md also no longer claims the wiki
holds no API documentation, which stopped being true with this commit.
.gitattributes matches the main repository's: every text file stored and
checked out LF, so a line-ending difference cannot show up as a spurious
diff on a page nobody edited.