I like Abraham's idea: >>Twitter could add: "next_cursor_string":"1314614526448841129"
Or a general return_as_string parameter which would return all values as strings. This would solve the problem for future values that might exceed the max int. There are going to be a lot of devs using PHP that don't have the option to switch to 64 bit or make any php.ini changes. On Sep 24, 12:29 pm, Dewald Pretorius <dpr...@gmail.com> wrote: > That magical maximum number appears to be 1000000000000 (1.0E+12). > > So, for tweet ids we still have a bit of breathing space. > > Dewald > > On Sep 24, 4:18 pm, Dewald Pretorius <dpr...@gmail.com> wrote: > > > Clearly PHP_INT_MAX plays no role in json_decode. > > > There must be some other mystical maximum number above which it > > represents the number as float in the decoded data. > > > Dewald
