summaryrefslogtreecommitdiff
path: root/malloc.c
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2004-06-13 14:57:25 +0000
committerSimon Tatham <anakin@pobox.com>2004-06-13 14:57:25 +0000
commita7963e261b59522cf57696b07058da760fb22e2e (patch)
tree7c53fc0df36973aa9142e0370774cbf3121fb5ff /malloc.c
parent0c4ba28a316e3c9c48bf52db3d2081634a8e61f7 (diff)
downloadhalibut-a7963e261b59522cf57696b07058da760fb22e2e.zip
halibut-a7963e261b59522cf57696b07058da760fb22e2e.tar.gz
halibut-a7963e261b59522cf57696b07058da760fb22e2e.tar.bz2
halibut-a7963e261b59522cf57696b07058da760fb22e2e.tar.xz
The Halibut manual contained at least one instance of two index
terms (intentionally) differing only in case, which were being silently folded into one by the case-insensitive index tag comparison. Halibut now warns in this situation (but then folds them anyway, which I think is better than silently generating an index containing many case-distinct forms of the same word - I imagine it's very easy to do that by mistake). The manual has been fixed to explicitly define distinct keywords (in the case I spotted and in five other cases picked up by the new warning!), and also documents this issue and how to work with it. [originally from svn r4279]
Diffstat (limited to 'malloc.c')
0 files changed, 0 insertions, 0 deletions