Re: [LAD] C - Change in memory causing seg.fault (but why?)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-dev@...>
Date: Friday, November 9, 2012 - 3:52 pm


> but for c I could not find much info on a potential difference.

If you look in the c standard or one of its drafts, e.g. this one:

In (pdf)page 111 (written page 99) you'll find:


6.7.2 Type specifiers


2 At least one type specifier shall be given in the declaration specifiers in each declaration,
and in the specifier-qualifier list in each struct declaration and type name. Each list of
type specifiers shall be one of the following sets (delimited by commas, when there is
more than one set on a line); the type specifiers may occur in any order, possibly
intermixed with the other declaration specifiers.
-- void
-- char
-- signed char
-- unsigned char
-- short, signed short, short int, or signed short int
-- unsigned short, or unsigned short int
-- int, signed, or signed int


-- unsigned, or unsigned int
-- long, signed long, long int, or signed long int
-- unsigned long, or unsigned long int
-- long long, signed long long, long long int, or
signed long long int
-- unsigned long long, or unsigned long long int
-- float
-- double
-- long double
-- _Bool
-- float _Complex
-- double _Complex
-- long double _Complex
-- struct or union specifier
-- enum specifier
-- typedef name


5 Each of the comma-separated sets designates the same type, except that for bit-fields, it is
implementation-defined whether the specifier int designates the same type as signed
int or the same type as unsigned int.

[end qoute]

I.e. "long" and "long int" designates the same type.

/Karl Hammar

Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
+46 173 140 57

Linux-audio-dev mailing list

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAD] C - Change in memory causing seg.fault (but why?), Karl Hammar, (Fri Nov 9, 3:52 pm)