Messages in this thread | | | Subject | Re: gcc fixed size char array initialization bug - known? | From | Andi Kleen <> | Date | 02 Aug 2007 23:06:44 +0200 |
| |
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> Hi > > I've run across the following gcc "feature": > > char c[4] = "01234"; > > gcc emits a nice warning > > warning: initializer-string for array of chars is too long > > But do a > > char c[4] = "0123"; > and - a wonder - no warning.
It's required by the C standard.
6.7.8.14 of C99: `` An array of character type may be initialized by a character string literal, optionally enclosed in braces. Successive characters of the character string literal (including the terminating null character if there is room or if the array is of unknown size) initialize the elements of the array. ''
Note the "if there is room".
I believe the rationale is that it still allows to conveniently initialize non zero terminated strings.
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |