RE : [lwip-devel] [task #7054] Clarification needed for variableinitialization

[Frédéric BERNON]

Yes, to my point of view, it's only the static and external. Perhaps the answer 
in one of these links...

http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1124.pdf 
http://www2.open-std.org/jtc1/sc22/wg14/www/C99RationaleV5.10.pdf
http://www.coding-guidelines.com/cbook/cbook1_0b.pdf (warning, big file)
  
====================================
Frédéric BERNON 
HYMATOM SA 
Chef de projet informatique 
Microsoft Certified Professional 
Tél. : +33 (0)4-67-87-61-10 
Fax. : +33 (0)4-67-70-85-44 
Email : address@hidden 
Web Site : http://www.hymatom.fr 
====================================
P Avant d'imprimer, penser à l'environnement
 


-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Goldschmidt Simon
Envoyé : mercredi 4 juillet 2007 17:29
À : lwip-devel
Objet : RE: [lwip-devel] [task #7054] Clarification needed for 
variableinitialization



> Follow-up Comment #6, task #7054 (project lwip):
> 
> http://savannah.nongnu.org/bugs/?20254
> 
> (Robert Ammerman wrote: )
> 
> "It is indeed part of the C standard that global variables
> without explicit initializers are set to zero.
> 
> However, talk about BSS or INITDATA is referring to some, but
> not all compilers. The way the compiler manages the 
> initialization is not defined. 
> For example, it would be perfectly valid for the 
> compiler/linker to generate
> 
> a bunch of assignment and "memset" type statements that are
> executed before main()"

Maybe I'm blind, I didn't find it in the ANSI C standard :-( But OK, we can 
then change initialization to reflect this. Not all are going to be happy with 
that, but those are broken compilers ;-)


Simon


_______________________________________________
lwip-devel mailing list
address@hidden http://lists.nongnu.org/mailman/listinfo/lwip-devel

Frédéric BERNON.vcf
Description: Frédéric BERNON.vcf