On Fri, 3 Aug 2007, Al Viro wrote: > It doesn't change the fact that use of c[4] or strlen(c) or strcpy(..., c) > means nasal demon country for you. Haha, funny. You, certainly, may think whatever you want, I'm anyway greatful to you and to all the rest for the trouble you took to find THE quote that actually answers the question. Thanks Guennadi --- Guennadi Liakhovetski - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: gcc fixed size char array initialization bug - known?
- From: Jan Engelhardt <[email protected]>
- Re: gcc fixed size char array initialization bug - known?
- References:
- gcc fixed size char array initialization bug - known?
- From: Guennadi Liakhovetski <[email protected]>
- Re: gcc fixed size char array initialization bug - known?
- From: Andi Kleen <[email protected]>
- Re: gcc fixed size char array initialization bug - known?
- From: Guennadi Liakhovetski <[email protected]>
- Re: gcc fixed size char array initialization bug - known?
- From: Stefan Richter <[email protected]>
- Re: gcc fixed size char array initialization bug - known?
- From: Guennadi Liakhovetski <[email protected]>
- Re: gcc fixed size char array initialization bug - known?
- From: Al Viro <[email protected]>
- gcc fixed size char array initialization bug - known?
- Prev by Date: Re: gcc fixed size char array initialization bug - known?
- Next by Date: Re: REGRESSION: serial_cs broken by 8250 changes
- Previous by thread: Re: gcc fixed size char array initialization bug - known?
- Next by thread: Re: gcc fixed size char array initialization bug - known?
- Index(es):
 |