Re: [ANNOUNCE] GIT 1.0.7

"H. Peter Anvin" [off-list ref] writes:

Any reason to not just do:

 	struct frotz {
 		int xyzzy;
 		char nitfol[1]; /* more */
 	};

... which should work on all compilers?

Laziness, especially to avoid having to deal with comments like
"your xmalloc(sizeof(struct frotz) + strlen(nitfol) + 1) should be
xmalloc(sizeof(struct frotz) + strlen(nitfol)), because you
have already one byte for nitfol element."

Junio C Hamano wrote:

"H. Peter Anvin" [off-list ref] writes:

quoted

Any reason to not just do:

	struct frotz {
		int xyzzy;
		char nitfol[1]; /* more */
	};

... which should work on all compilers?

Laziness, especially to avoid having to deal with comments like
"your xmalloc(sizeof(struct frotz) + strlen(nitfol) + 1) should be
xmalloc(sizeof(struct frotz) + strlen(nitfol)), because you
have already one byte for nitfol element."

In the case of strings, that's probably a blessing (already accounted 
for the null byte).

	-hpa