On 06.02.2013 00:17, Steve Bennett wrote:
I might be pointing out the obvious here, but isn't the bigger risk
that some software will fail silently rather than catastrophically?
Like, an editor tries to save node 2^32+100, and saves it as 100, or
something?
It is, but API requires you to provid
On Wed, Feb 6, 2013 at 7:13 AM, Andrew M. Bishop
wrote:
> Since 2^31 nodes will make older versions of some software unusable
> and 2^32 nodes will make other versions unusable it would be helpful
> to have a wiki page to record this information. I think that most
> useful would be a table of the
Hello Andrew,
On 05.02.2013 21:13, Andrew M. Bishop wrote:
Since 2^31 nodes will make older versions of some software unusable
and 2^32 nodes will make other versions unusable it would be helpful
to have a wiki page to record this information. I think that most
useful would be a table of the mi
Paul Norman writes:
> As of right now, we are 5.31 million nodes away from hitting our 2^31th
> node. This is likely to cause some software to break. Hopefully everything
> major has been tested, but if you haven't checked your software now would be
> a good time to do so. I think coastcheck will
On Mon, Feb 04, 2013 at 06:34:46PM -0800, Paul Norman wrote:
> As of right now, we are 5.31 million nodes away from hitting our 2^31th
> node. This is likely to cause some software to break. Hopefully everything
> major has been tested, but if you haven't checked your software now would be
> a good
5 matches
Mail list logo
