RE: Options for signed 64bit ints

["Chodera, Ian" <Ian.Chodera@...>]

nano = 10^-9

see: http://physics.nist.gov/cuu/Units/prefixes.html





-----Original Message-----
From: lua-l-bounces@lists.lua.org [mailto:lua-l-bounces@lists.lua.org] On Behalf Of Andrew Starks
Sent: 01 August 2013 04:41
To: Lua mailing list
Subject: Options for signed 64bit ints

I'm working with a library that deals in nano time (10^7 == 1 second).

I have to convert between clock many bases, which means getting very small or very huge numbers.

Simplicity would wash over me if I were dealing with 64-bit signed ints; the native C type. As it is, I'm complecting things in the service of avoiding common scenarios where I'm loosing precision.

So, if I decide that I can't live without 64bit signed ints: User data? Some kind of awesome library**?

lbc brings the openssl dependency, which is "a thing", especially on Windows. (don't know what openssl's license is, either).

Is there anything else out there that works with 5.2, or is this simple enough that I should just use the C-API and quit whining?

--Andrew


** Lua 5.3 Work1? This is for production, but this project won't see the light of day for about a year. If (most likely when, if history is a guide) we beat 5.3 to production, we'd have to go back-port some other method. Since this isn't a huge deal breaker, I'm okay with that risk, for even a small chance of success. That is, I kind of want to be talked into this option, but it seems to be lunacy, at this point in 5.3 development cycle.


**************************************************************************************** Note: If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. ****************************************************************************************