Bug#854560: ITP: node-max-timeout -- Max amount of milliseconds that can be passed to `setTimeout()`

To: 854560@bugs.debian.org
Subject: Bug#854560: ITP: node-max-timeout -- Max amount of milliseconds that can be passed to `setTimeout()`
From: Andrey Rahmatullin <wrar@debian.org>
Date: Wed, 8 Feb 2017 16:12:00 +0500
Message-id: <[🔎] 20170208111200.y2hb4jkml6x7fz24@belkar.wrar.name>
Reply-to: Andrey Rahmatullin <wrar@debian.org>, 854560@bugs.debian.org
In-reply-to: <[🔎] CAPL8bmo0qToU5Nx6xCU5HPhr+Qt_LDxN2NhYhcuKvgHNuymoqA@mail.gmail.com>
References: <[🔎] CAPL8bmo0qToU5Nx6xCU5HPhr+Qt_LDxN2NhYhcuKvgHNuymoqA@mail.gmail.com>

On Wed, Feb 08, 2017 at 04:34:28PM +0530, Abhishek Lolage wrote:
> Values larger than the one returned from this module, 2147483647 (~25
> days),
> are too big to fit into a signed 32-bit integer,
Yes, it just returns 2147483647.

-- 
WBR, wRAR

Attachment: signature.asc
Description: PGP signature

Reply to:

References:
- Bug#854560: ITP: node-max-timeout -- Max amount of milliseconds that can be passed to `setTimeout()`
  - From: Abhishek Lolage <abhisheklolage@gmail.com>

Prev by Date: Bug#854560: ITP: node-max-timeout -- Max amount of milliseconds that can be passed to `setTimeout()`
Next by Date: Bug#854570: ITP: node-bn.js -- Big number implementation in pure javascript: Required for browserify
Previous by thread: Bug#854560: ITP: node-max-timeout -- Max amount of milliseconds that can be passed to `setTimeout()`
Next by thread: Bug#854570: ITP: node-bn.js -- Big number implementation in pure javascript: Required for browserify
Index(es):
- Date
- Thread