[lkml]   [2007]   [Aug]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: gcc fixed size char array initialization bug - known?
On Thu, Aug 02, 2007 at 10:26:37PM +0200, Guennadi Liakhovetski wrote:
> Worse yet, K&R explicitely writes:
> <quote>
> char pattern[] = "ould";
> is a shorthand for the longer but equivalent
> char pattern[] = { 'o', 'u', 'l', 'd', '\0' };
> </quote>
> In the latter spelling gcc < 4.2 DOES warn too.

Does warn for what? Array with known size? Sure, so it should - you
have excess initializer list elements.

Note the [] in the quoted - it does matter.

Again, it's perfectly legitimate to use string literal to initialize
any kind of array of character type. \0 goes there only if there's
space for it; if array size is unknown, the space is left. That's it.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-08-02 23:13    [W:0.083 / U:5.544 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site