Terry Ellison

I am still testing the 5.1 backport on a dev build to put it through the Lua test suite clean. I've also done a full code review using meld against...

Getting your head around all of this isn't easy. I kept coming across fine details of the implementation and wondered why on earth is was coded that way. So I...

As I said in the issue, I don't really want to dick around with something that we want to remove.

Philip, forget 4. I am not going to do all the extra work to get an int-only version of Lua53 working and supported, when the current default does everything that...

> What came to me as a surprise was that the change on the dev branch was so backwards incompatible with master @pjsg Philip, I've been brooding about his one...

If you stay in integer then the overflow occurs at 2^31 -- same the old int builds. If you want mSec or uSec resolution, then why not just use the...

BTW most of these assign the result of a `lua_tonumber()` to an int (or `uint16` in the case of `mcp4725.c`) or `lua_pushnumber()` on an `int` argument. These are a sure...

Rather than have two threads discussing the same issue, and given that @pjsg has opened a second thread #3224 on this, I suggest that we pause discussions here and use...

I can see the +/- over this committer vs open debate, so I don't have a _strong_ view on this, but whatever the write access rules, the current state of...

Another point is that unlike MediaWiki (Wikipedia) the GitHub wiki has no concept of talk pages for contributors to discuss content pages; the only analogue is using an issue, so...