[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: operator overloading for string matching
- From: Chris Berardi <cberardi32@...>
- Date: Tue, 18 Aug 2015 07:41:00 -0400
On Tuesday, August 18, 2015, Dirk Laurie <dirk.laurie@gmail.com> wrote:
2015-08-17 21:22 GMT+02:00 Petite Abeille <petite.abeille@gmail.com>:
>> On Aug 17, 2015, at 9:15 PM, Dirk Laurie <dirk.laurie@gmail.com> wrote:
>>
>> But it won't work as expected when str1 and str2 both
>> are convertible to numbers.
>
> LUA_NOCVTN2S
> LUA_NOCVTS2N
Who on this list invokes "lua", their everyday Lua interpreter,
and what gets executed is Lua 5.3 compiled with those two
options on? Put up your hands, please.
I think it would be nice to be able to set these and other (currently only) compile time flags at runtime. Something like
set_flag(LUA_NOCVTS2N, true)
That way you're not beholden to how the interpreter was compiled to get a desired behavior.
