ISO C - revision history

Dank: /* Types */

2021-07-29T10:36:48Z

Types

← Older revision		Revision as of 10:36, 29 July 2021
Line 45:		Line 45:

	===tgmath.h===		===tgmath.h===
	~~===_Generic===~~
	C11 introduced the new keyword <tt>[https://en.cppreference.com/w/c/language/generic _Generic]</tt>, allowing one of several type-tagged expressions to be chosen based on the type of a controlling expression.
	===<tt>static</tt> in array parameters===		===<tt>static</tt> in array parameters===
	Beginning with C99, <tt>static</tt> can be inserted into array parameters ala:		Beginning with C99, <tt>static</tt> can be inserted into array parameters ala:

Dank at 10:28, 29 July 2021

2021-07-29T10:28:17Z

← Older revision		Revision as of 10:28, 29 July 2021
Line 15:		Line 15:
	* Implementations are "encouraged to ensure that representation of C and C++ atomic types is the same."		* Implementations are "encouraged to ensure that representation of C and C++ atomic types is the same."

	==Aliasing==		==Asserts==
			* <tt>_Static_assert()</tt> is evaluated at compile time, huzzah!

			==Generic dispatch==
			The new <tt>_Genetic</tt> keyword allows mapping the type of an expression to a set of expressions. This is mainly usable for type-based dispatch of the kind seen in <tt>tgmath.h</tt>. You can't, so far as I can tell, use it for true parametric polymorphism. Tony Finch demonstrates a clever use for [https://fanf.livejournal.com/144696.html parametric constness]:
			<code>
			#define strchr(s,c) _Generic((s), \
			const char * : (const char *)(strchr)((s), (c)), \
			char * : (strchr)((s), (c)))</code>

			==Types==
			===Aliasing===
	* See [[Compiler Design]] page		* See [[Compiler Design]] page
	* -O2 implies -fstrict-aliasing, at least as of gcc 4.3		* -O2 implies -fstrict-aliasing, at least as of gcc 4.3
Line 21:		Line 32:
	** 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

	~~==Types==~~
	===stdint.h===		===stdint.h===
	An excellent addition in C99. Type constructions of the form u?int{variety}_t (u prefix denotes unsigned). Varieties include:		An excellent addition in C99. Type constructions of the form u?int{variety}_t (u prefix denotes unsigned). Varieties include:

Dank: /* stdint.h */

2021-07-29T10:13:39Z

stdint.h

← Older revision		Revision as of 10:13, 29 July 2021
Line 29:		Line 29:
	* <tt>least{8,16,32,64}</tt>: Minimum native 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.		* <tt>{8,16,32,64}</tt>: Integer type having precisely this width.
			====inttypes.h====
			ugly <tt>printf</tt> specifiers for the types in <tt>stdint.h</tt>. e.g.:
			* <tt>printf("%"PRIu64"\n", some_uint64_tvar);</tt>

	===tgmath.h===		===tgmath.h===
	===_Generic===		===_Generic===

Dank: Dank moved page ISO C18 to ISO C: (1) it's C17 apparently(?) (2) future proofing

2021-02-24T05:30:47Z

Dank moved page ISO C18 to ISO C: (1) it's C17 apparently(?) (2) future proofing

← Older revision		Revision as of 05:30, 24 February 2021
(No difference)

Dank: /* Types */

2021-02-21T21:30:18Z

Types

← Older revision		Revision as of 21:30, 21 February 2021
Line 32:		Line 32:
	===_Generic===		===_Generic===
	C11 introduced the new keyword <tt>[https://en.cppreference.com/w/c/language/generic _Generic]</tt>, allowing one of several type-tagged expressions to be chosen based on the type of a controlling expression.		C11 introduced the new keyword <tt>[https://en.cppreference.com/w/c/language/generic _Generic]</tt>, allowing one of several type-tagged expressions to be chosen based on the type of a controlling expression.
			===<tt>static</tt> in array parameters===
			Beginning with C99, <tt>static</tt> can be inserted into array parameters ala:

			<code>
			void foo(int bararr[static 10]);
			</code>

			This indicates to the compiler that the array passed as <tt>bararr</tt> must have room for at least 10 elements. This ought help it produce diagnostics, and perhaps help code generation.

Dank at 19:08, 8 February 2021

2021-02-08T19:08:47Z

← Older revision		Revision as of 19:08, 8 February 2021
Line 6:		Line 6:
	* I'd like to further along [http://gcc.gnu.org/c99status.html gcc C99 support]		* I'd like to further along [http://gcc.gnu.org/c99status.html gcc C99 support]

	==~~Threads~~==		==Concurrency==
	* Hans Boehm's [http://www.hpl.hp.com/personal/Hans_Boehm/c++mm/ Threads and Memory Model for C++] page is awesome		* Hans Boehm's [http://www.hpl.hp.com/personal/Hans_Boehm/c++mm/ Threads and Memory Model for C++] page is awesome

			===Atomics===
			Introduced in C11, and exposed by <tt>stdatomic.h</tt>. Use <tt>_Atomic</tt> as a type specifier (ala <tt>volatile</tt> or <tt>const</tt>).
			* Unlike other type specifiers, an atomic form of a base type might have different size/alignment than the base type.
			* <tt>struct</tt>s and <tt>union</tt>s may be declared atomic, but it is then undefined behavior to access any of their members.
			* Implementations are "encouraged to ensure that representation of C and C++ atomic types is the same."

	==Aliasing==		==Aliasing==
Line 15:		Line 21:
	** 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==		==Types==
			===stdint.h===
	An excellent addition in C99. Type constructions of the form u?int{variety}_t (u prefix denotes unsigned). Varieties include:		An excellent addition in C99. 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>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).
Line 22:		Line 29:
	* <tt>least{8,16,32,64}</tt>: Minimum native 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.		* <tt>{8,16,32,64}</tt>: Integer type having precisely this width.
			===tgmath.h===
	==~~Atomics~~==		===_Generic===
	~~Introduced in~~ C11~~, and exposed by~~ <tt>~~stdatomic~~.h</~~tt>. Use <tt>_Atomic<~~/~~tt> as a type specifier (ala <tt>volatile<~~/~~tt> or <tt>const~~</tt>).		C11 introduced the new keyword <tt>[https://en.cppreference.com/w/c/language/generic _Generic]</tt>, allowing one of several type-tagged expressions to be chosen based on the type of a controlling expression.
	* Unlike other type specifiers, ~~an atomic form~~ of ~~a base~~ type ~~might have different size/alignment than~~ the ~~base~~ type.
	* <tt>struct</tt>s and <tt>union</tt>s may be declared atomic, but it is then undefined behavior to access any of ~~their members.~~
	* Implementations are "encouraged to ensure that representation of C and C++ atomic types is the same."

Dank: C11 atomics

2021-01-17T15:34:24Z

C11 atomics

← Older revision		Revision as of 15:34, 17 January 2021
Line 22:		Line 22:
	* <tt>least{8,16,32,64}</tt>: Minimum native 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.		* <tt>{8,16,32,64}</tt>: Integer type having precisely this width.

			==Atomics==
			Introduced in C11, and exposed by <tt>stdatomic.h</tt>. Use <tt>_Atomic</tt> as a type specifier (ala <tt>volatile</tt> or <tt>const</tt>).
			* Unlike other type specifiers, an atomic form of a base type might have different size/alignment than the base type.
			* <tt>struct</tt>s and <tt>union</tt>s may be declared atomic, but it is then undefined behavior to access any of their members.
			* Implementations are "encouraged to ensure that representation of C and C++ atomic types is the same."

Dank: Dank moved page ISO C99 to ISO C18: There have been at least three revisions since C99, heh

2019-08-03T20:33:13Z

Dank moved page ISO C99 to ISO C18: There have been at least three revisions since C99, heh

← Older revision		Revision as of 20:33, 3 August 2019
(No difference)

Dank: /* stdint.h */

2009-10-04T06:34:10Z

stdint.h

← Older revision		Revision as of 06:34, 4 October 2009
Line 16:		Line 16:

	==stdint.h==		==stdint.h==
	An ~~awesome~~ addition. Type constructions of the form u?int{variety}_t (u prefix denotes unsigned). Varieties include:		An excellent addition in C99. 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>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>max</tt>: Size sufficient to hold any other integer type.

Dank at 06:33, 4 October 2009

2009-10-04T06:33:50Z

← Older revision		Revision as of 06:33, 4 October 2009
Line 1:		Line 1:
	==[[GCC\|gcc]] ~~support for C99 language extensions~~==		==Compilers==
	* I'd like to [http://gcc.gnu.org/c99status.html ~~further this along~~]		* Intel's [http://software.intel.com/en-us/intel-compilers/ C/C++ Compiler] (icc) is [http://software.intel.com/en-us/articles/non-commercial-software-download/ free for non-commercial development]
			* AMD's [http://developer.amd.com/cpu/open64/pages/default.aspx Open64 Compiler Suite] is just plain free

			===[[GCC\|gcc]]===
			* I'd like to further along [http://gcc.gnu.org/c99status.html gcc C99 support]

	==Threads==		==Threads==