define a structure for object IDs
Many places throughout the code use "unsigned char [20]" to store object IDs (SHA-1 values). This leads to lots of hardcoded numbers throughout the codebase. It also leads to confusion about the purposes of a buffer. Introduce a structure for object IDs. This allows us to obtain the benefits of compile-time checking for misuse. The structure is expected to remain the same size and have the same alignment requirements on all known platforms, compared to the array of unsigned char, although this is not required for correctness. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
brian m. carlson committed
Mar 13, 2015 at 23:39 UTC
5f7817c85d4b5f65626c8f49249a6c91292b8513
1 file changed
+8
cache.h
+8
@@ -43,6 +43,14 @@ int git_deflate_end_gently(git_zstream *);
43
int git_deflate(git_zstream *, int flush);
44
unsigned long git_deflate_bound(git_zstream *, unsigned long);
45
46
+/* The length in bytes and in hex digits of an object name (SHA-1 value). */
47
+#define GIT_SHA1_RAWSZ 20
48
+#define GIT_SHA1_HEXSZ (2 * GIT_SHA1_RAWSZ)
49
+
50
+struct object_id {
51
+ unsigned char hash[GIT_SHA1_RAWSZ];
52
+};
53
+
54
#if defined(DT_UNKNOWN) && !defined(NO_D_TYPE_IN_DIRENT)
55
#define DTYPE(de) ((de)->d_type)
56
#else