UDI Environment: Difference between revisions

[unchecked revision]

Content deleted Content added

Inline

@@ Line 22: / Line 22: @@
 The Uniform Driver Interface declares specific-length types for use in arithmetic and logical operations. They have fixed lengths that don't change between different platforms.
+<source lang="C">
-. '''typedef unsigned char udi_ubit8_t'''
+typedef	uint8_t		udi_ubit8_t;
+typedef uint16_t	udi_ubit16_t;
+typedef uint32_t	udi_ubit32_t;
+typedef int8_t		udi_sbit8_t;
+typedef int16_t		udi_sbit16_t;
+typedef int32_t		udi_sbit32_t;
+typedef bool		udi_bool_t;
+</source>
+The driver must use these types while passing arguments and returning variables. They can also use the fast ints instead of the fixed width ones.
-. '''typedef unsigned short udi_ubit16_t'''
-. '''typedef unsigned int udi_ubit32_t '''
-. '''typedef char udi_sbit8_t'''
-. '''typedef short udi_sbit16_t'''
-. '''typedef int udi_sbit32_t'''
-. '''typedef udi_ubit8_t udi_boolean_t'''
-Driver must use these types at least while passing arguments and returning variables. They can '''internally use the ISO C types''' because that doesn't affect compatibility. For example, the long type is useful for getting the most optimized type for the architecture.
 ==== Abstract Types ====

Navigation menu