ISO C: Difference between revisions

From dankwiki
No edit summary
No edit summary
Line 10: Line 10:
* -Wstrict-aliasing=2 warns about many constructions unsafe to use with -fstrict-aliasing
* -Wstrict-aliasing=2 warns about many constructions unsafe to use with -fstrict-aliasing
** How to use Berkeley sockets API? See http://archives.free.net.ph/message/20080529.200047.b40321b6.fi.html, etc
** How to use Berkeley sockets API? See http://archives.free.net.ph/message/20080529.200047.b40321b6.fi.html, etc
==stdint.h==
An awesome addition. Type constructions of the form u?int{variety}_t (u prefix denotes unsigned). Varieties include:
* <tt>ptr</tt>: Size sufficient to hold a pointer. This is useful for function type definitions, when it's unsure whether a pointer or integer type would be most appropriate for various instances (a <tt>void *</tt>'s size is not directly related to an <tt>int</tt>'s size by the ANSI C standard).
* <tt>max</tt>: Size sufficient to hold any other integer type.
* <tt>fast{8,16,32,64}</tt>: Fastest integer type having at least the specified width.
* <tt>least{8,16,32,64}</tt>: Minimum native integer type having at least the specified width.
* <tt>{8,16,32,64}</tt>: Integer type having precisely this width.

Revision as of 22:05, 13 July 2009

gcc support

Threads

Aliasing

stdint.h

An awesome addition. Type constructions of the form u?int{variety}_t (u prefix denotes unsigned). Varieties include:

  • ptr: Size sufficient to hold a pointer. This is useful for function type definitions, when it's unsure whether a pointer or integer type would be most appropriate for various instances (a void *'s size is not directly related to an int's size by the ANSI C standard).
  • max: Size sufficient to hold any other integer type.
  • fast{8,16,32,64}: Fastest integer type having at least the specified width.
  • least{8,16,32,64}: Minimum native integer type having at least the specified width.
  • {8,16,32,64}: Integer type having precisely this width.