halibut/biblio.c, branch master My halibut tree Add missing initialisations in the 'word' structure. 2017-05-14T07:44:15+00:00 Simon Tatham anakin@pobox.com 2017-05-14T07:11:06+00:00 c00d1c3b6003dbbb72439de0ebdb4a93c8763f65 The 'breaks' and 'aux' fields were filled in rather inconsistently at various places where a word is created - especially the outlying ones that manufacture pieces of document during internal processing of contents, index, bibliography, cross-references etc rather than directly from the input file. This has never led to any user-visible behaviour change that I've noticed, but it made a lot of annoying noise in the valgrind output, which got in my way last week when I was trying to debug the CHM generation. 
The 'breaks' and 'aux' fields were filled in rather inconsistently at
various places where a word is created - especially the outlying ones
that manufacture pieces of document during internal processing of
contents, index, bibliography, cross-references etc rather than
directly from the input file. This has never led to any user-visible
behaviour change that I've noticed, but it made a lot of annoying
noise in the valgrind output, which got in my way last week when I was
trying to debug the CHM generation.
Revamp of the Halibut error handling mechanism. 2012-08-29T18:13:11+00:00 Simon Tatham anakin@pobox.com 2012-08-29T18:13:11+00:00 1489dc15967970576d08f3f2b22c6e1c939bcbcf I'm not quite sure why I ever thought it was a good idea to have a central variadic error() function taking an integer error code followed by some list of arguments that depend on that code. It now seems obvious to me that it's a much more sensible idea to have a separate function per error, so that we can check at compile time that the arguments to each error call are of the right number and type! So I've done that instead. A side effect is that the errors are no longer formatted into a fixed-size buffer before going to stderr, so I can remove all the %.200s precautions in the format strings. [originally from svn r9639] 
I'm not quite sure why I ever thought it was a good idea to have a
central variadic error() function taking an integer error code
followed by some list of arguments that depend on that code. It now
seems obvious to me that it's a much more sensible idea to have a
separate function per error, so that we can check at compile time that
the arguments to each error call are of the right number and type! So
I've done that instead.

A side effect is that the errors are no longer formatted into a
fixed-size buffer before going to stderr, so I can remove all the
%.200s precautions in the format strings.

[originally from svn r9639]
Yikes! Stack trash I'd never noticed before. Oops. 2004-04-12T08:29:15+00:00 Simon Tatham anakin@pobox.com 2004-04-12T08:29:15+00:00 e9d2a1681a1ba9fa9cee79e197e6d62c3deae7b7 [originally from svn r4056] 
[originally from svn r4056]
Rename Buttress to Halibut. I _think_ I've caught everything in this pass. 2002-08-05T10:31:35+00:00 Simon Tatham anakin@pobox.com 2002-08-05T10:31:35+00:00 c478f3d9469c09773097eba89342c311ee70a319 [originally from svn r1800] 
[originally from svn r1800]
Configurability backbone, and first use of it 1999-11-07T17:28:56+00:00 Simon Tatham anakin@pobox.com 1999-11-07T17:28:56+00:00 6dff7b9ee671925f8c5dae1cd34bdc55f3236c38 [originally from svn r275] 
[originally from svn r275]
First backend! Text output now pretty much works. 1999-10-20T20:17:18+00:00 Simon Tatham anakin@pobox.com 1999-10-20T20:17:18+00:00 8511f4ae900f48999617bc8384e9c327673e2196 [originally from svn r240] 
[originally from svn r240]
More development... 1999-09-12T15:38:06+00:00 Simon Tatham anakin@pobox.com 1999-09-12T15:38:06+00:00 9972b0f0d1ce6e08ce6f9505980c9c889ae994bc [originally from svn r220] 
[originally from svn r220]