I noticed this when I straced something; we're doing 1-byte writes.
This reduced the time for "make check" from 12m37s to 11m48s.

If you've not got gcc, this is a bit of a lose.  But for everyone else,
it's far simpler.

Doing our own parsing lost a few lines of code, too.

Our coverage is over 99% now.

This was for lockcheck, but that didn't work very well.  Seems like a useful
addition nonetheless.

With correct seed, we could expand hash and break test.

Paul Wayper points out that "or" has a better mental mapping, and more
importantly that this is how Perl's Getopt::Long does it.

I'm still leaving the - and -- in there, for reasons previously articulated
(grep-friendly and harder to get wrong).

In particular, gcc warns about cast from int to pointer.

Instead, directly control write().

%.* => unsigned, not size_t.

%zu for size_t printf.

Make sure we use 1UL to bitshift, not 1.

printf's %.* means an unsigned arg, not a size_t.

check_free_list returns a length, not bool.

Particularly useful for reproduction, like tdbtorture.

      
If a Swedish-speaking Finn writes code in English, why should I complain about
a few weird spellings?

(Was succeeding in finding "Free bucket 8" string, because of "Free bucket 80:".

Now we get long options!

The former encapsulates a common "just exit on error" case, the latter
avoids having to repeat the extra usage string.

(We actually would have crashed before if someone passed NULL there, even
 though the documentation said you could).

A little less typing for users.

compiler, list, noerr, sparse_bsearch, str, str_talloc, stringmap, talloc_link, tdb, tdb2, typesafe_cb: fix examples

Phew, now they call compile!

Now (with fixes) every ccanlint example compiles!

      
      /**
       * struct foo - some description
      
So, <identifier> here can have a space in it.

      
This hit my doc extraction tool, so fix it!