Re: [NTG-context] integer displayed as .0 float in Lua-5.3

2018-08-11 Thread Alan Braslau
On Sat, 11 Aug 2018 11:29:41 +0200 Pablo Rodriguez wrote: > On 08/09/2018 10:16 PM, Alan Braslau wrote: > > On Thu, 9 Aug 2018 22:00:48 +0200 > > Pablo Rodriguez wrote: > > > >> I guess that backwards compatibility should be important here, but I > >> hope there are stronger reasons for

Re: [NTG-context] integer displayed as .0 float in Lua-5.3

2018-08-11 Thread Hans Åberg
> On 11 Aug 2018, at 11:33, Pablo Rodriguez wrote: > > On 08/09/2018 10:20 PM, Hans Åberg wrote: >>> On 9 Aug 2018, at 21:20, Pablo Rodriguez wrote: >>> [...] >>> My background is in humanities and I don’t understand the exponent for >>> being a float ("10²" contains an exponent >>>

Re: [NTG-context] integer displayed as .0 float in Lua-5.3

2018-08-11 Thread Pablo Rodriguez
On 08/09/2018 10:25 PM, Hans Hagen wrote: > In addition to what others already explained, you should not depend on > features that are implementation dependent or might disappear. Many thanks for your detailed explanation, Hans. I had no idea that the automatic conversion from string to number

Re: [NTG-context] integer displayed as .0 float in Lua-5.3

2018-08-11 Thread Pablo Rodriguez
On 08/09/2018 10:20 PM, Hans Åberg wrote: >> On 9 Aug 2018, at 21:20, Pablo Rodriguez wrote: >> [...] >> My background is in humanities and I don’t understand the exponent for >> being a float ("10²" contains an exponent >> [https://www.m-w.com/dictionary/exponent], but I would say is an integer

Re: [NTG-context] integer displayed as .0 float in Lua-5.3

2018-08-11 Thread Pablo Rodriguez
On 08/09/2018 10:16 PM, Alan Braslau wrote: > On Thu, 9 Aug 2018 22:00:48 +0200 > Pablo Rodriguez wrote: > >> I guess that backwards compatibility should be important here, but I >> hope there are stronger reasons for breaking it. > > tonumber() provides backwards compatibility. And the