search for: c_variable_types_and_declarations

...write code that doesn't break on other systems, I am assuming the "worst case". Hence I have to deal with the overflow... Is my information that "int" can be 16bit (a) false or (b) true but not valid for any relevant architecture? Quote from http://en.wikipedia.org/wiki/C_variable_types_and_declarations#Size A short int must not be larger than an int. An int must not be larger than a long int. A short int must be at least 16 bits long. A long int must be at least 32 bits long. In my words: 16 bit <= short <= int <= long >= 32 bit I know for a fact that my ints are 32bits long, but I...

> what happens if this number flows over? It is just a "int", so it might reach > its limits at 2^15 = 32768, that happens after 102 puts... I would say that an int is 32 bits :-) Actually, RTP defines the timestamp as a 32-bit value. Now, what happens when it overflows (3 days for narrowband), I don't know what the RFC says about it. > In my current > implementation