| commit | 826c778f7c3bd6c8356a8ecfd1cb0e4326fcf1d8 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Wed, 29 Nov 2017 23:51:41 +0000 (30 00:51 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 5 Dec 2017 21:37:43 +0000 (5 13:37 -0800) | ||
| tree | 24d40fd01c10d696c3faadf26b7fa1584bcfcebc | treesnapshot (tar.gz zip) |
| parent | 9b185bef0c15cec1ea8753ce091e42ea041f2c31 | commitdiff |
hashmap: adjust documentation to reflect reality
The hashmap API is just complicated enough that even at least one
long-time Git contributor has to look up how to use it every time he
finds a new use case. When that happens, it is really useful if the
provided example code is correct...
While at it, "fix a memory leak", avoid statements before variable
declarations, fix a const -> no-const cast, several %l specifiers (which
want to be %ld), avoid using an undefined constant, call scanf()
correctly, use FLEX_ALLOC_STR() where appropriate, and adjust the style
here and there.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The hashmap API is just complicated enough that even at least one
long-time Git contributor has to look up how to use it every time he
finds a new use case. When that happens, it is really useful if the
provided example code is correct...
While at it, "fix a memory leak", avoid statements before variable
declarations, fix a const -> no-const cast, several %l specifiers (which
want to be %ld), avoid using an undefined constant, call scanf()
correctly, use FLEX_ALLOC_STR() where appropriate, and adjust the style
here and there.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| hashmap.h | diffblobblamehistory |