> > If you are on a Perl that does not have 64-bit int and you are not using > > the stringified *_str fields, you may have overflowed the Perl precision > > limit this morning, which bit TTYtter users hard. Just a friendly warning > > to check your code, or use BigInt if you can rely on that support. > > Cameron, I'm not experiencing any problems in Net::Twitter applications. > As long as "id". All of JSON::Any backends (JSON::XS, typically) result > in a value that maintains its full precision as long as it's used in a > string context. Am I missing something that's going to bite me (and > therefore Net::Twitter users in general)?
If you're treating it purely as a string, no (but I don't know how JSON::* handles things that appear to be integer values, and "id" is not stringified itself in the raw JSON). -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Actually, we can overcome gravity (just not the paperwork involved). ------- -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk